Tie connects to your Google Ads and Meta Ads accounts for two reasons. It sends your store's events straight from Tie's servers to each platform, and it keeps customer audiences in each platform up to date. This page explains what that means, what Tie sends, what access we ask for, and how to turn it off.
Both connections are optional. Your Tie setup is complete without them, and you can add them whenever you run those channels.
What Tie does in each account
Server-side conversions. When someone views a page, views a product, adds to cart, starts checkout or buys, Tie sends that event to Google Ads and Meta from our server-side tracking. Because the event does not depend on the visitor's browser, it is not lost to ad blockers, browser privacy settings, a script that fails to load, or a tab closed too early. Google and Meta get a fuller picture to learn from.
Audiences. Tie also syncs audiences of shoppers it has identified. In Google Ads these are Customer Match audiences, and in Meta they are Custom Audiences. You can use them for targeting, exclusions and lookalikes the same way you use any other audience.
Bot filtering. Tie filters out non-human traffic before events are sent, so bots do not inflate your conversion counts or your audiences.
What Tie sends
Event | Google Ads | Meta |
Page view | Pageview | Pageview |
View a product | ViewItem | ViewContent |
Add to cart | AddToCart | AddToCart |
Start checkout | BeginCheckout | InitiateCheckout |
Purchase | Purchase | Purchase |
Tie sends these directly from its servers, so you will not see them in your browser's network tab or in your own tag manager.
What shows up in your accounts
In Google Ads, Tie creates a small set of conversion actions, one per event above. You may see them labeled with an RR prefix, which is short for Revenue Roll, Tie's legal entity name. Tie sets these up as secondary conversion actions, and they stay secondary. Secondary actions are reported for measurement and do not drive your campaigns' bidding, so connecting Tie does not change how your bids are optimized.
In Meta, Tie sends events to a new pixel set up for Tie, separate from any pixel you already run, and you can see them in Events Manager. Audiences appear in your Custom Audiences list.
You can check delivery yourself in Google Ads under Tag Diagnostics, and in Meta Events Manager.
Will my reported conversions change?
They can go up after Tie goes live, particularly purchases. That reflects orders your browser-based tracking was missing, not new traffic. Let your finance and marketing teams know before launch so the change is not a surprise.
Tie runs alongside your existing tracking and does not replace it. In Google Ads, keep only one purchase action feeding any given conversion goal, so a purchase is not counted twice.
What access Tie needs, and who connects it
Someone on your team with admin access to the ad account connects it from the Onboarding page in your Tie account. Tie cannot connect it for you.
Google Ads. You enter your 10-digit Customer ID. Tie sends a link request from its manager account, and you accept it in Google Ads. You also sign in with a Google user who can see that account.
Meta. You enter your Ad Account ID, accept two Meta terms for audiences, and sign in to Meta as an admin of the ad account, approving the permissions Meta shows.
The step-by-step guides walk through each one.
You can connect as soon as your domain is added on the Onboarding page. You do not have to wait for DNS to verify. Conversions begin flowing once your domain and the Tie Pixel are live.
How to remove it
Open the Onboarding page, find the Google or Meta card, and choose Disconnect. Disconnecting unlinks Tie from the ad account and shuts down the related integration. You can reconnect at any time.
Disconnecting does not delete what Tie already added. The Google Ads conversion actions and the audiences Tie created stay in your accounts, and you can remove them yourself if you no longer want them.
Questions
If something here does not match what you see in your account, reach out to your Tie contact.