By default, the ad tags for your placements will look something like this:

<ins id="my-tag1" style="padding:0px;"></ins>
<script type="text/javascript">
var avxt = {
  tag: "my-tag1", // The ID of the element on the page the ad should be loaded in
  network: "yourdomain", // .sites.avrtix.com
  site: 1, // ID of your site
  placement: 2, // ID of your placement
  size: "300x250", // Size of the placement (width x height)
};(avrtix=window.avrtix||[]).push(avxt);if(1!=window.avrtixLoaded){window.avrtixLoaded=!0;var a="https:"==location.protocol?"https:":"http:",b=document.createElement("script");b.type="text/javascript";b.async=!0;b.src=a+"//cdn.avrtix.com/v1/async.min.js";(document.getElementsByTagName("head")[0]||document.getElementsByTagName("body")[0]).appendChild(b)};
</script>

This ad invocation code will by default make a request to ssp.avrtix.com, which is our domain, but you can change this! All it takes is 2 quick steps:

1. Create CNAME record

Create a new subdomain (or domain) and give it a CNAME record that points to ssp.avrtix.com . The reason we want you to point to our domain is that it's routing traffic to our nearest datacenter location. This way, your visitors will always have the lowest latency!

2. Update your ad tag

In your ad tag, in the avxt object, simply add a new line before }; with:

  host: "yourdomain.com"

Make sure you're only using your domain/subdomain that has the CNAME record you created earlier. Do not add any protocol, trailing slashes or paths. Only the domain.

Place these new ad tags on your website, and you're good to go! If you inspect your network traffic, you will see requests are made to your own domain instead of ours.

How to deal with SSL/HTTPS?

We can create the necessary SSL certificates and update our servers to allow full HTTPS for both the whitelabeled ad serving domain and CDN domain. An extra one-time fee may be necessary if you want to use this option – check your MSA or contact your account manager.

Can I change the CDN domain?

You may have noticed that the ad tag will load our invocation script from cdn.avrtix.com , though it's possible to change this as well! There are two ways we can do this:

Option 1: Create a CNAME record

You can create a CNAME record and point it to cdn.avrtix.com . This requires you to contact your account manager and let them know what your new CDN domain will be. An extra one-time fee may be necessary if you want to use this option – check your MSA or contact your account manager.

For this option, do a simple search and replace cdn.avrtix.com  to your new CDN domain.

Option 2: Mirror our CDN

You can also use your own CDN and mirror our CDN. This will make you fully in control of the domain and SSL certificates, but this also means you have to ensure uptime and low latency yourself, and the costs associated with this.

For this option, do a simple search and replace cdn.avrtix.com/v1/async.min.js  to your new CDN domain and path to the script.

Why are there still requests made to domains that are not mine?

As we get help from 3rd parties with everything from ad-serving to tracking, there might be requests made to other domains we are not able to control or cover over.

Did this answer your question?