> For the complete documentation index, see [llms.txt](https://docs.podplay.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.podplay.app/marketing/ads-integrations/attribution-with-ads-data.md). # Attribution with Ads Data ### Ad Campaign Attribution Data Is Incomplete or Missing Ad campaign attribution for Meta Ads or GTM with PodPlay covers Web App conversions out of the box. It does not extend to the iOS or Android App. To capture ad-driven conversions that complete in a native phone App, your Club needs to integrate an "App Attribution Partner" like [Branch](https://www.branch.io/) or [AppsFlyer](https://www.appsflyer.com/) at your own cost. #### Symptoms When might you need an App Attribution Partner? * Order events (actions performed by the Customer) show blank context values (no web, front desk, iOS, or android tag) * Web Order events are missing Source, Medium, or Campaign data * Looker Studio or BigQuery reports show low attribution coverage * iOS appears overrepresented in raw counts with little campaign breakdown #### The Three Paths from Ad to Booking A Customer who sees an ad can reach a completed booking in three ways. Out of the box, only the first preserves attribution end-to-end without an App Attribution Partner: 1. Click the ad and complete the purchase in the Web App — attribution captured. 2. Click the ad, interest increases, Customers walk into the Club, and the staff at the front desk books a Reservation — attribution lost in the offline handoff. 3. Click the ad and download or open the iOS or Android App, then book through the App — attribution lost when the journey moves out of the browser. This applies to Customers who already have the App, too. If an ad is served to a Customer with the App installed and they tap the ad, the App opens to handle the URL and the connection between ad and conversion breaks at the OS level. The same Customer can still book through the Web App, in which case the booking lands in the trackable bucket. #### Cause The Context patch labels every Order Event as `web`, `front desk`, `iOS`, or `android` based on the Segment common spec, which makes the source visible in reports. It does not restore attribution data lost on non-web paths. Events without a Google client ID come from the App or Front Desk and carry no Source, Medium, or Campaign by design. Other gaps you may see include Private Event signup links generated by Admins (captured as web traffic even though the source was front-desk activity), outdated Android or iOS App versions that don't pass the Context value to Segment, and ad blockers stripping UTM parameters from web Customers (these account for roughly 20% of missing web Source/Medium/Campaign data). #### Bridging the Gap with an App Attribution Partner Apple's iOS attribution model and the analogous Android setup require a paid third-party service to capture ad conversions that complete inside the App. Google maintains a list of certified App Attribution Partners that integrate with Google Ads and other ad platforms — see the [App Attribution Partner overview](https://support.google.com/google-ads/answer/12961402). PodPlay has experience with Branch. AppsFlyer is another widely used option in the same category and is worth comparing on pricing and feature fit before you commit. Both appear on Google's App Attribution Partner list. What you should know before signing a contract: 1. Your Club pays for the third-party subscription. PodPlay does not bundle or cover any cost within Ads Attribution (entirely optional based on a Club's preference to dive further in to this data). 2. PodPlay builds the integration into the iOS App and the Android App. The web, iOS, and Android codebases are separate, so this requires dedicated iOS and Android developer time and needs to be sequenced against other roadmap work (timelines cannot and are not provided on when the integration can be completed for your environment). 3. After the integration ships, some App attribution paths will still break in ways that aren't predictable in advance. Apple's privacy framework introduces edge cases that surface only in production (once the integration is set to capture the standard paths, PodPlay will not chase individual journey flows that break). 4. The integration captures ad-to-conversion data. It does not change how Reservations, Events, or Memberships work in the App (the Customer's booking flow is not updated to meet requirements of any requests from an App Attribution Partner). #### What You Can Do Now 1. Confirm `context.channel` is mapped to the Context custom dimension (in Segment, done by PodPlay) for both backend and web sources so the source labels show up in your reports. 2. Encourage Customers to update their Android App so Context values flow through. 3. Turn on Google Analytics inside ActiveCampaign Automations (or your Club's marketing tool of use) to track clicks from email campaigns. This is the closest substitute for App attribution on email-driven journeys until a third-party service is in place. 4. Use Meta Ads and Google Ads native conversion tracking and audience reporting to guide spend decisions without App-level attribution. 5. If Looker Studio is your reporting destination, consider holding off on building App-attribution dashboards until the third-party integration is in place. The data won't exist to populate them yet. {% hint style="info" %} Web attribution covers the majority of new Customer ad clicks, since new Customers typically don't have a native phone App yet and complete their first booking in the Web App. Returning Customers, who make up roughly 78% of completed Reservations (variance on completed Reservations depends on your Club's retention of Customers), mostly book through the App. If your campaigns target returning Customers (for example, email automations to existing Customers with active Memberships), then App attribution will matter more for you than for a Club running primarily new-Customer acquisition campaigns. Data on returning Customers is available in the Analytics+ package, so paying an App Attribution Partner becomes redundant. {% endhint %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.podplay.app/marketing/ads-integrations/attribution-with-ads-data.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.