Conversions API Gateway for Multiple Accounts: Prospective Agencies FAQs
Q: AWS vs. GCP? Which one should we use?
A: The Signals Gateway product built on Google Cloud Platform (GCP) is more stable and cost-effective compared to Amazon Web Services (AWS). However, if your team can secure a hardware deal with AWS, you may be able to reduce costs by using this provider. Similar deals may also be available through GCP. Ultimately, if your tech team prefers to proceed with AWS, this option will most likely be acceptable. Currently, the Conversions API Gateway does not support GCP onboarding via Meta Events Manager.
Q: How should we charge advertisers?
A: The Conversions API Gateway does not offer any pre-built feature that can give a cost estimate for hosting client accounts. For instance, other agencies may charge for a single pixel versus unlimited pixels. However, we do provide event count metrics that can be used to estimate costs. If the client has specific requirements, we can prioritize and add them to our roadmap.
Q: What is the difference between an agency installation vs. an advertiser installing themselves?
A: Advertisers will have to manage and pay for the instance if they install it themselves. With an agency installation, the advertiser is hosted within the agency’s existing setup.
Q: What about the deduplication of events?
A: Event ID is needed for deduplication. Web events from browsers pass event_id for the events sent to Meta and Signals Gateway.
Q: What is the difference between an instance installed from Events Manager vs. using a direct installation template?
| Installation Type | Cloudflare or ACM required to add first account | Supports multiple accounts |
|---|---|---|
Events Manager | Not required for AWS. Cloudflare setup required for GCP. | Yes |
Directly install using template | Not required for AWS. Cloudflare setup required for GCP. | Yes |
Q: Why do I need Cloudflare?
A: Conversions API Gateway AWS-EKS and GCP solutions support a limited number of client first-party domains. These limits are 25 for AWS-EKS and 15 for GCP. We need Cloudflare to support more client first-party domains. Cloudflare can support up to 5K such domains.
Q: Can we add multiple accounts without Cloudflare?
A: You can install up to 21 accounts without Cloudflare. If you want more than 21 accounts without Cloudflare, you will then need to install the old version 1.9.4 (only for AWS). This solution will add additional computation capacity on the instance, not the individual hosted client accounts. See this document for reference.
Q: Can we set up a custom domain using an existing Cloudflare domain?
A: Setting up a custom domain based on an existing Cloudflare domain will work, but it is preferred that you register a new domain on Cloudflare and then proceed with a custom domain setup.
Q: Does an end advertiser also need to complete Cloudflare setup?
A: No, that setup is required for the host account. The end advertiser must set up domain routing and set entries on their DNS server.
Q: Will end advertiser websites see traffic going to Meta?
A: No, traffic will be seen going to the host domain or custom advertiser domain.