Ad accounts and tracking
Two things have to exist before an ad can run: an account on the network that will bill the spend, and a way to count the results. Growth offers two ways to get the account, and one consent-first way to count.
Two ways to run ads#
| Bring your own account | Managed by Autoflowly | |
|---|---|---|
| Who pays the network | You, directly, on your own Google Ads or Meta invoice | Autoflowly, from prepaid credit you top up |
| Setup | One consent screen per network: sign in, grant the ads permission | None; an account is created for you under Autoflowly's manager |
| Where the data lives | Your account; you can see everything on the network's own console | A client account under Autoflowly's manager, reported in the Grow tab |
| Good for | Businesses that already advertise, agencies, anyone who wants the raw console | Owners who never want to see an ad console |
| Availability | Rolling out with ad launch | After network reviews |
When both exist for an app, your own account wins.
Connecting your own account#
- In the Grow tab, choose Connect Google Ads or Connect Meta.
- Sign in on the network's own page and grant the ads permission. For Google, the YouTube upload permission is requested as well, so launch videos can be uploaded for video campaigns.
- Pick the ad account if you have several.
The permission is separate from the Google or GitHub sign-in you use for Autoflowly itself; signing in to Autoflowly never grants ads access. Tokens are stored encrypted and can be revoked from the Grow tab or from the network's security settings. Autoflowly never holds ad money in this mode: the network bills you.
Managed accounts and the wallet#
In the managed option you top up a wallet on the web (card, through Stripe Checkout). Campaigns start only with credit, each day's spend is debited once, and an empty wallet pauses everything until you top up. The phone shows the balance but does not sell top-ups, in line with store rules. Managed accounts open once Google and Meta have completed their reviews of Autoflowly as an advertiser of record; until then the tab offers bring-your-own.
Conversion tracking, consent first#
To know whether an ad produced a booking, the networks need a signal from your app. Growth sets this up once per account: a Google conversion action for your metric and a Meta pixel.
How it behaves for your visitors:
- Your app shows a small cookie bar in your accent colour. Nothing from Google or Meta loads until the visitor accepts.
- Click identifiers (the
gclidandfbclidparameters) are kept on the visitor's device so a conversion can still be attributed if they accept later in the session. - The conversion fires on the real confirmation page of your metric: the booking confirmed, the order placed, the sign-up completed.
- A visitor who declines is counted in your app's own numbers, not in the networks'. Growth's scorecard uses your app's real metric first, so declined consent does not make the goal look worse than it is.
This matches how consent works under the ePrivacy rules and GDPR in the EU and UK, and it is the same behaviour whether your account is your own or managed. See Privacy and GDPR.
What is reported#
| Where | What |
|---|---|
| Grow tab, scorecard | Spend per channel, impressions, clicks, conversions, your app's metric, pace against the goal, the day's proposal |
| Phone, Grow screen | Progress and the next decision |
| Weekly report | A growth block |
| Network consoles | Everything, when the account is yours |
Disconnecting#
Disconnect an account from the Grow tab. Live campaigns are paused first. Managed accounts keep their credit until you ask for it to be refunded.