03 · Tracking and app setup
What we found and fixed before launch
Before 10/30 the website sent no conversions to Meta, Google Ads or GA4. A site script blocked the Meta pixel and a bug in the Google tag stopped every Google hit. App installs in AppsFlyer had been at zero since 9/16. Their historical numbers were missing, not low.
Website
- Old Meta pixel belonged to an unknown business and could not be shared. Created a new pixel in their business portfolio, Martin swapped it in on 10/30.
- Found and diagnosed the Google tag bug (tested live). Martin shipped the fix 10/30. GA4 and Google Ads now record.
- New GA4 property set up with the team and client as admins, plus key events: sign up, create job, purchase.
- Event spec sent to Martin: sign up, create job, purchase with market, service and first booking. Live since 10/30.
- Server-side token (CAPI) issued to Martin for bookings that are auto-charged (about 27% of paid bookings).
- Domain verified in Meta.
Apps
- No Meta app existed. Created one in their business portfolio for iOS and Android.
- Connected AppsFlyer to Meta and to Google Ads for both customer apps.
- Found why installs were zero: AppsFlyer moved to a free plan without attribution on 9/16. Martin recommended the paid plan and the client handled billing.
- App events (sign up, create job, purchase) built by Martin, release on Zach's go.
- iOS SKAN setup pending until app events ship.
Audiences and billing
- Uploaded Sam's list of 3,725 past customers and excluded them from every ad set.
- Targeting tilted to 55+ (Zach said most customers are 60+), 15 miles around each campus.
- Card added by Zach 10/30. Meta bills new accounts about every $6, which can trigger bank declines like the one on 11/6.