Skip to content

Integrations Settings

Here you can control certain preferences:


The contents of this field will show up when a user hovers over the option on the tag config page. This allows you to explain to the user what this option is.


Use filters to control the options available at a tag config level. For example, if you have multiple organisations and a GAM account for each, you could connect them all at the parent level and restrict each integration to its appropriate organisation. Or even filter out our default GAM option if you are SaaS only.

This removes the chance of human error where the wrong ad server is selected because there are multiple options available to select.

You can include or exclude both organisation and publishers.

Note; excluding an organisation does not hide it from the list of integrations on the integrations management page. Users with access to integrations can still see it and can modify the filters at any level of your organisation hierarchy.

Ads.txt Requirements

Here you can optionally input your line-separated ads.txt requirements for this integration. This will do several things when selected inside a tag config:

  1. Each publisher will see these ads.txt lines listed as go-live requirements (preventing issues before they can happen)
  2. We check the status of all our publisher's ads.txt daily and flag anything that is missing in the UI for all to see
  3. We send out a report once a week to publishers highlighting any missing ads.txt lines
  4. You can view the status of ads.txt completeness across your network via your health report


We have three available macros for use when an ads.txt line needs to contain publisher information as part of it, these are:

  • __UID__ -- This is the publisher's unique ID inside the Content Ignite system
  • __OID__ -- The ID of the publishers parent organisation
  • __PID__ -- The ID of the highest parent organisation
  • __ID1__ -- In the case of GAM, this is the Network ID
  • __ID2__ -- In the case of GAM, this is the MCM ID
  • __UID_DOMAIN__ -- The publishers domain
  • __OID_DOMAIN__ -- The domain of the publishers parent organisation
  • __PID_DOMAIN__ -- The domain of the highest parent organisation

These can be used to include the ID in the ads.txt line:, __UID__, DIRECT

This will be substituted for each publisher, so for a publisher with UID 12345, they will see the following requirement in their ads.txt section:, 12345, DIRECT

If the macro is empty, for example, no MCM ID has been entered, that entire line will be left out.

Direct vs Reseller

Have direct relationships with some publishers, but indirect with others? This often means different ads.txt lines.

To accommodate this, we have two flags that can be inserted before an adx.txt line so our system can make the correct choice for each publisher. The first part is correctly setting the "Managed" status of each child organisation, where managed means you have a direct relationship.

Then for any lines that need to change based on this, you can add [managed] or [unmanaged] before it. For example:

[managed], 160530, DIRECT, 5d62403b186f2ace
[unmanaged], 160530, RESELLER, 5d62403b186f2ace, 539625136, RESELLER

For the above, the first line will only show for managed publishers, the second line will only show for unmanaged publishers, and the last line will show for all publishers.