Client Invite
Create one branded link to request client access to ad, analytics and commerce accounts.
What it does
What it does and who uses it Client Invite gives agencies and freelancers a single, branded link to request access to clients’ ad, analytics and commerce accounts so clients can approve needed permissions without sharing passwords. It’s used during onboarding to replace multi-step instructions and manual permission exchanges. Single branded access link Create one invite link that bundles multiple access requests into a single client flow. Clients click the link, sign in to their accounts and approve the permissions the agency requests, reducing back-and-forth when onboarding new accounts. Supported platforms and request modes Client Invite supports Meta (Facebook/Instagram/Business Manager), Google products (Google Ads, GA4, Tag Manager, Search Console, Merchant Center), Shopify, LinkedIn and other platforms. The product classifies each platform’s request type as Automatic (API grants), Hybrid (API plus extra client action) or Manual (instructions/links the client completes), and surface-level guides explain the different flows. API, webhooks and workflow automation When a client grants access, the platform can emit webhooks and be queried via an API so agencies can connect the event to onboarding workflows, CRMs, sheets or messaging tools. Developer documentation describes endpoints, webhook payloads and example recipes; the docs note automation features are plan-gated. Client-facing branding and experience Invite pages and screens are configurable with agency branding so the client-facing flow presents a consistent, professional interface. Customizable visual elements and the single-link format are intended to reduce confusion and build trust during the access approval process. Limitations and manual steps to expect Not every asset is fully automatable. The documentation states some assets or platforms require manual steps or extra client actions, and Client Invite provides step-by-step guides where manual completion is necessary. Also, automation capabilities such as API and webhooks are limited to certain plans per the docs.
