Connections

Both platforms are connected the same way, from Settings > Connections:

1. Click Connect next to Meta or Google.
2. You are redirected to the platform's own sign-in and consent screen. Your Meta or Google password is entered there, on their site, and never passes through pimads.
3. You approve the requested permissions and are redirected back.
4. The platform hands pimads an access token, which pimads stores and uses for every later API call on your behalf.

After connecting, pick which ad account the workspace should use in Settings > Ad account.

pimads asks for the permissions needed to manage advertising, and uses them for exactly two things:

• Reading campaign structure and performance data: campaigns, ad sets and ad groups, ads, keywords, budgets, and the metrics behind the dashboard, analytics, rules, and AI features.
• Writing the changes you make in pimads: status changes, budget edits, targeting and creative updates, new negative keywords, and so on. Writes only happen when you (or a rule you explicitly approved or set to auto mode) trigger them.

pimads never posts organic content, never touches assets outside the bound ad account, and never shares your ad data with third parties. The one nuance worth knowing: small ad-performance snippets are sent to our AI processing service to generate insights, described on the AI features page.

Access tokens are stored server-side, encrypted with AES. They are decrypted only at the moment an API call is made. Tokens are never sent to your browser and never appear in logs.

Meta issues long-lived tokens that still expire after a while. pimads renews them automatically in the background before they expire, so a healthy Meta connection stays healthy without you doing anything. Google connections use refresh tokens, which do not need this treatment.

A connection can still break: you change your platform password, revoke the app on the platform side, lose access to the ad account, or a token expires while renewal is not possible. When that happens, API calls start failing and pimads notifies you. To fix it, go to Settings > Connections and run the Connect flow again. Your workspace, rules, and settings are untouched; reconnecting only replaces the stored token.