Documentation

Set up AdsTracker in four parts: your organization, your Google Ads data, your revenue postbacks and your alerts.

Getting started

Create your organization, invite your team, and set roles.

  1. Start a free trial and create your organization.
  2. Invite teammates as leads or buyers. Roles are enforced at the data layer: a buyer sees only the accounts they own, a lead every account in their team.
  3. Once your team is in, bring in your Google Ads data to set up your first accounts.

Bring in your Google Ads data

Add your accounts and start sending statistics.

  1. Add an account, then open its script.
  2. Paste it into Google Ads under Tools and settings, Scripts.
  3. Schedule it hourly. That schedule is what makes spend, clicks, conversions and approval status appear.
  • The current script is version 23, and since version 21 the start, stop and budget commands reach every campaign type. A version bump needs one manual re-paste per account, which the accounts table tells you about.
  • AdsTracker never signs into your account: anything that changes there is run by that script, from a command you or one of your rules queued, and bids are never set by us.

Webhooks & script

Send revenue and conversion events into AdsTracker.

  • Statistics arrive on a per-account webhook signed with its own secret.
  • Revenue arrives on a postback URL carrying its own token, which your tracker or affiliate network calls server to server.
  • Sub-ID parameters on that call are what attribute revenue to a creative and a traffic source.
  • Every payload is verified, rate-limited and idempotent, so a repeated request is never counted twice.
  • That is why ROI comes from your own postbacks: we do not invent revenue.

Alerts

Get notified on anomalies, silent accounts, and approval drops.

  • Set rules on overspend, zero conversions, an ROI drop, a banned account, a silent script or an approval drop, plus statistical anomaly rules and composite rules that combine several conditions.
  • Delivery is Telegram and the notification centre inside the app, with browser push for the critical ones. There is no email channel.
  • Threshold, priority and cooldown are yours per rule.
  • Quiet hours are set once for the organization, and a daily digest collects what quiet hours held back.