Connecting Google Ads lets Tie deliver server-side conversions to your account. It is a quick connection, and you can do it now. It does not wait on anything else. Google will start receiving real conversion data once your domain is connected and the Tie Pixel is live.
Step 1: Connect Google in the Tie dashboard
Log in to the Tie dashboard, or go to Integration Setup.
Find the Connect Google card, click Proceed, and follow the prompts.
Step 2 (fallback): Link via Tie's manager account
If the dashboard connection is not available for your account:
Share your Google Ads account ID (the 10-digit ID in the top corner of Google Ads) with your Tie contact.
Tie sends a link request from its manager account (MCC)
797-354-7695. Accept it in your Google Ads notifications.
About the conversion actions Tie creates
Once connected, Tie creates a small set of conversion actions in your account, covering page view, view item, add to cart, begin checkout, and purchase. You may see them labeled with an RR prefix. That is short for Revenue Roll, Tie's legal entity name (see the Onboarding FAQ for more on this).
These fire from Tie's own server-side tracking, not from a tag anywhere on your site, so you will not find a matching tag in your own tag manager. Each one fires once per event, covering your full order and traffic volume rather than a filtered subset.
If you already track purchases another way, Tie's purchase numbers can read slightly higher. That is expected. Our server-side delivery is not exposed to the things that quietly drop a browser-based conversion, like ad blockers, browser privacy protections, a script failing to load, or someone closing the tab before a tag fires. If the difference looks larger than that, check whether the two actions use the same count setting (every conversion vs. one) and conversion window, since a mismatch there widens the gap on its own.
Because it is the more complete count, we recommend making Tie's purchase action your primary conversion action, and demoting your own purchase event to secondary. Demote it rather than deleting it, so you keep the comparison.
The other Tie actions, page view, view item, add to cart and begin checkout, are measurement signals. Leave those secondary.
One thing to get right. Tie's conversion actions are not deduplicated against the ones you already have, so only one purchase action should feed any given conversion goal. If both land in the same goal, that goal counts every purchase twice.
Good to know
Connection status shows on your Integration Setup page, and Tie validates the connection as part of going live.