Google Meta Ads Conversion Tracking
See which Google and Meta ads bring paying customers, from your Zendesk sales.
Trabaja con
Support
Desarrollador
Unwired LogicAbout this app
Your ads get clicks. Zendesk knows which enquiries became sales. This app connects the two.
When a ticket reaches an outcome you choose (a won order, a booking, a completed job), the app tells Google Ads and Meta which ad that customer came from and what the sale was worth. Your campaigns learn which clicks become customers.
What you'll be able to answer
- What does a customer cost, per campaign?
- Which campaigns bring nobody?
- Which ads bring the customers who spend the most?
Want it set up for you?
We do the setup in about an hour, with no developer needed on your side. Book a 45-minute demo and we'll walk through it on your own Zendesk.
Key features
- Works from your Zendesk triggers. A conversion is sent when your business process says so, not when a page loads.
- You choose what counts. Each trigger sets its own conversion name, value and currency, for Google, Meta or both.
- Customer details stay protected. The ad click ID alone is enough to match a sale. If you include email or phone, they're scrambled (SHA-256 hashed) before they're sent.
- Respects consent. Each customer's consent choice is honoured, and each ad click converts only once per event type.
- No API keys to manage. You give the app's service account access in Google Ads, and you can remove it there at any time.
- See every decision. A Recent uploads view lists every conversion sent or skipped for 90 days, with the reason, and notes each upload on the ticket.
Data handling and security
Data exchanged. Your trigger sends the click identifier, a conversion name, and optionally an order reference, value, currency, email and phone. Email and phone are hashed with SHA-256 before reaching Google or Meta. Nothing is read back from Zendesk except the name of whoever grants access; all it writes is an internal note per upload.
Credentials. Your customer id, Meta credentials and Zendesk grant are encrypted at rest per installation (field-level AWS KMS), and never shown again.
Access control. Restrict the app to the Admin role at install, under Enable role restrictions, and Zendesk loads it for nobody else. Your receiver URL is unique per account and every request is signature-verified. TLS throughout.
Permitted use. Data is used solely to upload your conversions - never for advertising, profiling, resale or training AI models.
About Unwired Logic
Unwired Logic has been a Zendesk partner since 2017, with 100+ Zendesk projects and teams in Tokyo and Bali. We build and run the connection, and you and your marketer decide what to do with the numbers.
Support
Setup guide | Privacy Policy | Terms of Service | support@unwiredlogic.com
Detalles de la aplicación
Cómo instalar
The setup guide has the request body to paste and the Google and Meta prerequisites in full. Allow about an hour.
Step 1: Install
Install the app and tick Enable role restrictions, selecting Admin - that decides who can open it. Then open it from the left nav bar and connect Zendesk access: that grant is what lets the app note each upload on its ticket. The other steps work without it.
Step 2: Get the ad click into Zendesk
Only your website can do this: your enquiry form must store the click id and UTM source on the Zendesk user - the setup guide lists the fields. Tag every campaign's landing URL with utm_source (google, facebook, instagram or meta); that value picks the platform, and Google auto-tagging will not add it.
Step 3: Connect Google Ads, Meta Ads, or both
Google Ads - enter your Customer ID. There is no key to paste: copy the service account address shown there and add it as a Standard user under Admin > Access and security, accepting the customer data terms. Conversion actions must be the offline / API-upload kind, not website tags.
Meta Ads - enter your Dataset ID and a Conversions API Access token.
Use Test connection on each; neither records a conversion.
Step 4: Create the webhook
Copy the Receiver URL from Webhook setup - unique to your account, so treat it as a secret. In Admin Center > Apps and integrations > Webhooks, create one webhook pointing at it, method POST, format JSON. Paste its signing secret back into Webhook setup and save; requests are rejected until you do. One webhook covers every conversion.
Step 5: Create your triggers
Per conversion, create a trigger with the conditions describing that outcome, add Notify active webhook, choose your webhook, and paste the request body from the setup guide. Give each a distinct eventType: that separates conversions in reporting and deduplication.
Step 6: Check it is flowing
Recent uploads lists every conversion decided on, newest first - skipped and rejected included. Click a row's ticket to open it. Send a ticketId and each upload is noted on that ticket too.
Troubleshooting
You cannot see the app - your role is not in its role restriction. A Zendesk admin can change that in Admin Center > Apps and integrations.
Conversions not appearing - each row in Recent uploads says what happened. Click id invalid points at Step 2, No action named at your trigger's body, Credentials missing at Step 3.
Nothing listed at all - check the webhook's delivery log in Admin Center. A rejected request means either the signing secret does not match, or the trigger sent no click id at all, which points at Step 2.
Help - support@unwiredlogic.com
Dejar una evaluación
Comparte tu experiencia con el resto de la comunidad Zendesk