Enabling CDN Domain for Signals Gateway Pixel Use

Updated: Jan 12, 2026

Amazon Web Services Cloudfront CDN service will be enabled for Signals Gateway Pixel customers starting from version 1.13. For those installed with a previous version and not using Cloudflare for the domain management, this guide includes instructions for activating CDN domains in an AWS account manually to finish the upgrade to the Signals Gateway product.

Enabling CDN through Cloudfront can significantly enhance client experience when accessing customers’ websites, due to the global caching of static content, resulting in faster access times compared to systems that do not use a CDN domain. Furthermore, it can decrease the Signals Gateway’s workload, as files will no longer be fetched from these gateways.

Activation CDN in Cloudfront

1. Make sure you have already upgraded to the Signals Gateway from the Conversions API Gateway (The upper left logo in the main page is not Meta logo).

2. Go to your AWS account and navigate to the Cloudfront screen, then Search Distribution by your "fallback domain". Note: Fallback domain can be found in your DNS setup page. If you know your cluster ID, you can directly choose it.

3. Go to the distribution by clicking the ID, and go to the "tags" tab. Confirm the Application is "Conversions API Gateway".

CloudFront distribution Tags tab showing the Application tag set to Conversions API Gateway

4. Go to the Behaviors tab, and click the Create Behavior button. In the behavior, set the values as below:

Create behavior Settings with Path pattern /*.js, eksbastion origin, HTTP and HTTPS, and GET, HEAD methods

Cache key and origin requests using CachingOptimized cache policy, AllViewer origin request policy, and SecurityHeadersPolicy

Function associations section with all four event types set to No association and the Create behavior button

Note: Origin and origin groups: [The first choice: “eksBastionInstanceCapigDistributionOriginxxxx”]

5. Under Create cache policy, set the value as below:

Create cache policy form naming capigCachingPolicy with TTL settings of 1800 minimum and 3600 maximum and default

Note: you can select your preferred Name and Description, and have TTL settings as 1800/3600/3600. All the others remain default.

6. Go back to the behaviors view, refresh cache policy, and select the new caching policy above.

Behavior Cache policy set to the new capigCachingPolicy with AllViewer origin request policy selected

7. Create the behavior. The final behaviors should match those shown in the image below:

Behaviors tab listing the /*.js behavior with capigCachingPolicy above the Default behavior for the distribution

8. A CDN domain for static .js files will now be enabled.