Before Day 1
Day 1 moves fast once you start. Use this ~30-minute window ahead of time to confirm provisioning and line up what you need.
Your domain is added to Anima
Anima is multi-tenant — you'll only see the domain(s) that have been provisioned for your account.
Confirm:
- Log in to the portal.
- Click Account at the bottom of the main sidebar to switch to Account mode.
- Open the account selector at the top of the sidebar. Your domain should be listed there (either directly, or under the customer account that owns it).
If your domain isn't listed:
- Contact your onboarding specialist (they'll provision it)
- You can skim the portal in the meantime, but you can't copy the wrapper tag or link GAM until the domain exists
There's no "add a domain" button in the portal today. Domain provisioning is handled by your onboarding specialist — usually within a business day of your kickoff call.
What you'll need for Day 1
Google Ad Manager access
- Admin access to the GAM network — you'll need to add Anima's service account under Admin → Access & authorization → Users
- Your GAM Network ID (visible in GAM under Admin → Global Settings)
- A clear picture of which role you'll grant the service account (Trafficker is typically sufficient; Administrator if you want Anima to manage line items)
If you're not the GAM admin on your team, loop in whoever is before Day 1.
Site deployment access
- Ability to edit your site's
<head>— either directly in code, via CMS, or through a header-scripts plugin - A way to deploy and purge cache. Full-page caching (CDN, Varnish, CMS cache) is the most common reason a correctly-pasted tag doesn't show up
Time block
Plan ~2 hours for Day 1. Most of it is waiting on GAM sync completion and testing the install — the active work is short but benefits from focus.
Who you'll be working with
| Contact | When |
|---|---|
| Onboarding specialist | Provisioning, Day-1 setup escalations, first-week questions. Usually the person who ran your kickoff call. |
Support (support@animaadtech.com) | Post-launch issues, bug reports |
| Account manager | Strategic questions, contract, partnership, optimization guidance |
For issues discovered in the browser, the in-app AI Assistant (sidebar in both modes) can help triage.
Sandbox / staging
A few options for testing without touching production:
- Staging domain — if you have a staging copy of your site, ask your onboarding specialist whether to use the same domain ID or provision a separate one. Same domain ID works; separate is cleaner if you want to isolate analytics.
- Debug mode on production — for verification, append
?pbjs_debug=trueto any URL. This enables wrapper debug logs in your Console without affecting anyone else's experience. See Wrapper Debugging. - Wrapper experiments — once you're live, use Wrapper → Experiments to roll out config changes to a percentage of traffic rather than 100%.
What the portal looks like
Two sidebar modes, toggled at the bottom of each sidebar:
- Main mode (Ad Manager) — Dashboard, Inventory, Demand, Integrations, Wrapper, Templates, AI Assistant
- Account mode (Account) — Setup (GAM, Wrapper, Core Web Vitals, Privacy, User Sync, Supply Chain, Custom Dimensions)
Day 1 work happens mostly in Account mode. Day 2 onward is mostly Main mode.
For exact paths referenced throughout these docs, see UI Paths.
Ready
Next: Your First Day →
Connect GAM, install the wrapper tag, verify.