Marketing

Open the ad-level policy detail inside the campaign's single ad group; if the UI still shows no reason, raise a Google Ads support chat quoting campaign 22766205539. Fix or appeal whatever the restriction is, and hold all iOS spend increases until the campaign serves clean.

Answers: The iOS campaign is limited by policy with five-figure lifetime spend and zero conversions ever — nothing else about iOS can be judged until it can serve.

The $1 Directions default was set to "Don't use a value" on 10 Aug 2026 — that lever is pulled, and demoting the action is locked on Google-hosted local actions. What remains is the real half: dynamic value and currency on the GA4 purchase event from the online store and the app purchase event, which first needs the purchase event routed to the account's own property (see the access ticket).

Answers: Reported ROAS over the window counts $1-a-piece placeholder actions; zeroing stopped the pollution going forward, and only real transaction values replace it with truth.

One Suppy ticket naming GTM container GTM-M36FG4C4 and GA4 property 438359162: edit rights on the container, visibility of the property. With access, route the purchase event to the business's own GA4 property (373805818) and install the Meta Pixel + Conversions API in the same container. Then prove the path: one test transaction through the online store landing in Google Ads and Meta with its real value.

Answers: The store runs a container the business does not control — the purchase event never reaches the property Google Ads imports from, and no Meta Pixel exists at all. Access, not development.

Firebase / GA4 SDK in both builds, install and first_purchase events imported to Google Ads as primary conversions, App Store Connect and Play Console linked to the ad account, SKAdNetwork conversion-value schema defined for iOS.

Answers: The largest app campaign reports zero installs — nothing can be optimised, cut or defended until the events reach the platform.

Pixel plus server-side Conversions API on the online store with deduplicated purchase, add-to-cart and begin-checkout events; Meta SDK app events for install and purchase; domain verified and the aggregated event schema ordered by value. Blocked on edit access to the store's GTM container — same Suppy ticket as the purchase routing.

Answers: No Meta Pixel exists on the storefront at all (fbq undefined, 10 Aug check) — the channel cannot optimise towards, or even see, a single conversion.

Archive 9H | Dave | Pmax, 9H | App promotion | Android and 9H | Video now — orphaned when the agency was removed 11 Sep 2025, no decision needed. For August Web Drive, Sales-Performance Max-1 and Groceries delivered at home: hold until the purchase event reaches the account's property, then review each campaign's ads, keywords and landing pages before any switch-on — re-enabled earlier they buy unmeasured traffic at $95/day.

Answers: Three of the six paused campaigns are agency leftovers to close out; the other three are a budget decision that only makes sense once purchases can be measured.

Set the four hidden Firebase actions (iOS + Android first-open and in-app purchase) to ENABLED through the Google Ads API (ConversionActionService) or a support ticket — the account UI offers no path to them, and the setup wizard would duplicate rather than unhide. Sequence after the iOS policy fix; then leave a fortnight before judging.

Answers: The app's own conversion actions exist and are HIDDEN — but unhiding cannot help a campaign that is not serving, so this follows the policy resolution.

Add Maltese to the Android campaign's language list, or drop its restriction so it matches iOS's all-languages setting — do NOT copy Android's six languages onto iOS, which would narrow the broader campaign. Separately, mirror the “Malta 2” audience signal onto iOS. Device targeting is not actionable on App campaigns. Account work, sequenced after the policy and tracking fixes.

Answers: Android excludes Maltese on a Malta-targeted campaign, and iOS runs with no audience signal — but neither matters while the account cannot measure conversions.

Inventory of every conversion action in Google Ads and Meta with its category, count and value rule; purchases separated from engagement events; one primary action per goal and everything else set to secondary.

Answers: One campaign counts conversions an order of magnitude cheaper than the rest, so the account's headline ROAS is not comparing like with like.

One naming convention across both channels (channel · goal · audience · creative · date), UTM template applied at account level, and a rolling test plan of one variable per flight with the decision rule written before launch.

Answers: Goal classification currently has to be inferred from campaign names, and every finding on this page would be sharper if the account said what it was for.