AMP: RTC

Select from the tabs below to view the indicated information. Read and follow all of the instructions to ensure that your integration goes smoothly.

Introduction

Introduction

These instructions have been provided to assist with adding Freestar RTC tags to your existing AMP Ad RTC configuration

Freestar test page for AdUnit positioning - http://demo.freestar.com/amp

Example of the tags and components we provide - https://l.t13.io/5hgj

The documentation provided is an example of what your code may look like. Please use the tags provided by your Onboarding Specialist or Customer Service Manager to ensure that your site-specific tags are used.

What you are going to need

  • An AMP page that you are already running AMP Ads on
  • Freestar AMP RTC Tags & Components (Public URL) - Provided by your Onboarding specialist

What the tags and components do

NOTE:

Not all of these will apply to your setup as RTC setup - if you have any questions please reach out to your OnBoarding specialist.

  • AMP components - These allow the various components and tags provided to deliver onto your AMP page 
  • Consent blocking meta-tag - this will stop personalised ads from showing if consent has not been captured and sent upstream
  • CMP & Geo override - this component captures user consent to allow targeted ads to deliver - It also ensures the CMP is only delivered in GEO’s that require it
  • Privacy settings - allows a user to alter their privacy settings at a later time
  • Privacy CSS - determines which re-prompt link should be shown
  • Cookie Sync - Allows SSPs to set user syncing cookies for targeted advertising
  • Cookie Sync CSS - will prevent the user agent styles from adding whitespace to the User Sync iframe
  • AdTags - 1-4 - these deliver MPUs 300x250 ads
  • AdTag - 5 - this deliver a double MPU - 300X600
  • AdTag - Sticky - a permanently displaying unit with refresh enabled to maximise yield
  • AdTag - Flying Carpet - this delivers an scrolling double MPU 

Additional considerations:

  • If you are using our Sourcepoint CMP solution - ensure you have updated your DNS record to the final endpoint.
  • Copy and paste the tags and components exactly as they are 
  • The AMP components, consent blocking meta tag, CMP & Geoveride and the Cookie Sync need to be present on every AMP page
  • Placement of AdTags should be planned out to ensure optimal yield and user experience
  • Reach out to your dedicated OnBoarding specialist for any guidance required 

GAM Service Access

GAM Service Access

These instructions have been provided to assist with providing Freestar the relevant GAM access to enable our RTC line items in your GAM instance.

What you are going to need:

  • Google AdManger

Steps to grant Service Access

  1. Sign into Google AdManager
  2. Click the Admin section
  3. Click Global settings
  4. Make sure to check the API Access box
  5. Click the green button “Add A Service Account User” (see screenshot below, note: it’s blue now)
  6. Enter the following
    1. Name: Freestar API Access
    2. Email Address: data-engineering@freestar-157323.iam.gserviceaccount.com
    3. Confirm Email Address: data-engineering@freestar-157323.iam.gserviceaccount.com
    4. Choose the role of Administator
    5. If the publisher is on GAM 360, they will have to add the team “All entities” to the service account once it is set up
  7. Click Save

Note:

We must have full administrative access in order to operate our scripts. Our scripts set nothing live automatically, and all orders and line items can be reviewed by the client before being set live. The scripts we run will set up 5 orders and a total of 2,000 line items. GAM limit is 61,000 active line items, so if they have a complex GAM setup it’s wise to check on where they are before we run our scripts. Go to Admin > Global Settings > Limit tab at the top to see.

CNAME

CNAME

Note:

  • This only applies if you are using our Sourcepoint CMP solution

These instructions have been provided to assist with setting up a CNAME.   Certain browser environments restrict the use of 1st party cookies (e.g. Safari's ITP) and limit our ability to persist user consent records for a longer period of time. In order to side step the restrictions you have the option to set cookies through the server rather than having to rely on document.cookie. This is true for our AMP and website implementations. To accomplish this, you need to set up a CNAME DNS record for a 1st party subdomain and include it in the AMP or website's configuration snippet.

What you are going to need:

  • Access to your DNS records
  • The information provided below

Setting up your CNAME DNS record

  1. Set up a 1st party subdomain and create a CNAME record pointing to cert.privacy-mgmt.com (notify your Onboarding specialist that this has been done)
  2. We suggest the subdomain be t13 - so it would read t13.examplesite.com
  3. Freestar notifies Sourcepoint that the CNAME record has been set up.
  4. Sourcepoint establishes a TLS certificate for the CNAME record.
  5. Sourcepoint then creates an account specific CDN endpoint - cdn-1638.privacy-mgmt.com.
  6. Sourcepoint then notifies Freestar that the CDN endpoint has been set up.
  7. Finally, you update the CNAME record to point to the new Sourcepoint CDN endpoint. This is cdn-1638-2.privacy-mgmt.com

AMP Components

AMP Components

Advise:  

  • Avoid duplicating any script tags as these will cause validation errors
  • <script> tags should be grouped together in the <head> of the page

Steps:

  1. Copy the AMP components provided
  2. Go to the opening <head> tag on your page and locate any pre-existing <script> tags 
  3. Paste them in


Meta Tag

Meta Tag

Advise:  

  • <meta> tags should ideally be grouped together in the <head> of the page
  • If using an external CMP provider - please reach out to them for guidance on if the Consent blocking meta tag ios required

Steps:

  1. Copy the consent blocking meta tag provided
  2. Go to the opening <head> tag on your page and locate any pre-existing <meta> tags 
  3. Paste in the consent blocking meta tag

CMP

CMP

Advise:

  • The CMP & GeoOverride should ideally live under the opening <body> tag

Steps:

  1. Copy the CMP & GeoOverride components provided
  2. Go to the opening <body> tag on your page
  3. Directly under the opening <body> tag - paste the CMP & GeoOverride

User Sync

User Sync

Advise:

  • UserSync component MUST be placed under the opening <body> tag otherwise it will not work.
  • Also referred to as Cookie Sync

Steps:

  1. Copy the UserSync component provided
  2. Go to the opening <body> tag on your page (where the CMP & GeoOverride has just been installed)
  3. Directly under the CMP & GeoOverride tag - paste in the User Sync

Privacy Settings

Privacy Settings

Steps:

  1. Copy the Privacy settings component provide
  2. Locate the opening <footer> tag on your page 
  3. Paste in the Privacy Settings

CSS

CSS

Advise:

  • There are two sets of CSS rules required, one set for the Privacy Settings and one set for the User Sync

Steps:

  1. Copy the CSS rules provided (this will take two runs)
  2. Locate the CSS rules in the <head> of your AMP page
  3. Paste the CSS rules

Ads.txt

Ads.txt

These instructions have been provided to assist with uploading an ads.txt file - there are lots of variations - if you have a different setup or any question please reach out to your OnBoarding specialist.

What is ads.txt:

Ads.txt = Authorized Digital Seller - It is a list of all partners authorized to sell the site inventory. The ads.txt list is saved as a text file and uploaded to the root domain of your site.

What you are going to need:

  • Ads.txt file provided

Steps to add to ads.txt to a .txt file:

  1. Create an ads.txt file on your site
  2. Add the ads.txt file provided
  3. Place the file in your HTML root domain
  4. Push latest changes to the live site

Steps to add to ads.txt to Wordpress

  1. Install the ads.txt Manager plugin on your Wordpress site
  2. Left menu bar - hover over settings > select Ads.txt
  3. Paste the ads.txt file provided
  4. Save settings

Dynamic Adas.txt

Why we use Dynamic Ads.txt?

We utilize a dynamic ads.txt product so that you will always have the most up-to-date version of ads.txt. To add this you will need to create a redirect to a file on our servers. Using our Dynamic Ads.txt will remove the monthly task of you having to update manually.

When should your Ads.txt file be updated?

Your ads.txt lines should be updated on your root domain (https://yoursite.com/ads.txt) a minimum of 2 days before your expected launch date. Freestar's Google ads.txt line needs to be in place before you can test our code on your test environment or page. For best results, we recommend that you update to use our dynamic ads.txt with all of Freestar's lines during testing as we already added your current provider's lines.

How to find your dynamic ads.txt redirect URL

  1. Login to the Freestar Dashboard.
  2. Select the 3 lines icon in the top left to open the left menu.
  3. Select Site Configuration in the left menu.
  4. Next to the site that you would like to edit select the "View Fs Ads.txt" button in the main section of the page.
  5. Copy the URL in your address bar.
  6. Follow the steps below in "How to set up Dynamic Ads.txt" to redirect your ads.txt from https://yoursite.com/ads.txt to the redirect URL you copied.

How to set up Dynamic Ads.txt

Find instructions in the Freestar Dashboard

  1. Login to the Freestar Dashboard.
  2. Select the 3 lines icon in the top left to open the left menu.
  3. Select Site Configuration in the left menu.
  4. At the bottom of the page, you will find instructions for the different methods for creating a redirect. Select the tab that is appropriate for your setup.

If you are unable to log in you can find the instructions on how to implement this here.

How to edit your custom Ads.txt lines when using Dynamic Ads.txt

For the lines that are specific to your site and outside Freestar's portfolio, you can either edit this in the Freestar Dashboard or ask your Onboarding Specialist or Customer Service Manager to add them to your custom file. 

To update in the Freestar Dashboard
Watch a demo of how this is done here.

  1. Login to the Freestar Dashboard.
  2. Select the 3 lines icon in the top left to open the left menu.
  3. Select Site Configuration in the left menu.
  4. Next to the site that you would like to edit select the "Edit Fs Ads.txt" button in the main section of the page.
  5. Add a new line to the top or bottom of your file.
    1.  Use # at the beginning of any comment lines.
      • Note: It is very important that you do not delete any of your existing lines without checking with your Freestar representative as some lines are very important and may cause ads to stop serving if removed.
  6. Select Save Ads.txt.

RTC Config

RTC Config

Advise:

  • If you are unsure where these should be placed - please reach out to your Onboarding specialist for guidance.

Steps:

  1. Copy one of the Tags provided
  2. Locate the AMP AdTag you want to add Freestar to
  3. Locate the rtc-config in the AMP Ad tag
  4. Paste in the code