Your ads. Your pixel.
Your numbers.

Yours. You paste your own Meta pixel ID, Google tag and TikTok pixel code, and the events land in your own accounts, where you already build your audiences and run your campaigns. Drry does not sit in the middle and does not take a cut of what those ads earn you.

No, and it is built so it cannot. Pixels load on your public pages only: your funnels, your bio link and shop, your public guides and event pages, and your join page. They never load inside the community feed, in a lesson, in direct messages, in your coach console, or on a form you have embedded on somebody else's site. That list is enforced by a test, not by good intentions.

Meta and TikTok conversions are sent from our server, off the Stripe payment we have already verified, rather than from the visitor's browser. That means an ad blocker or a browser privacy setting does not cost you the sale, and the amount reported is the amount actually charged. Google works differently: reaching Google Ads from a server needs its Ads API, a developer token and your own OAuth approval, which we do not ask you for, so Google conversions fire in the browser with the conversion label you set. Each network gets exactly one copy of each conversion, so nothing is ever counted twice.

Visitors in the EU, the EEA and the UK are asked before any pixel loads, on a banner styled from your own theme, and nothing loads until they agree. Anyone can change their mind from the control that stays on the page. We keep a record of the choice so you can show it was offered, holding no IP address, no fingerprint and no identity. When you connect a pixel you are the data controller for it, so your own privacy notice governs it.

We report the refund, and a chargeback you lose, as its own event on Meta and TikTok, carrying the amount that went back. What that does NOT do is remove the original purchase from your reporting: neither network gives a website any way to withdraw a conversion it has already reported, and negative values are rejected, while Google's equivalent needs a level of API access we do not have. So treat it as visibility rather than correction. It is genuinely useful for two things: seeing which campaigns bring refund-prone buyers, and building an audience of refunders to exclude, so your ads stop hunting for more people like them.

Two ways, both in the console. There is a Send test event button for Meta and TikTok that posts a real event to your account while you watch, and a delivery line under each network showing how many conversions reached it in the last thirty days, with the network's own error message if any did not. A revoked token says so instead of quietly producing nothing. If you paste the test event code from your ad account first, those test sends go to its Test Events tab instead of your live reporting, so you can check the whole thing works without putting a single fake number in front of a real decision.

Growth. The pixel configuration is owner-only, because it involves a credential to your ad account and a decision about sharing visitor data, and that is not a decision to hand to every admin.