Skip to article

Integrations

Snapchat

A Snap Business organization and an active ad account you can access

Ownership and availability

You own the Snap Business organization and ad account. Obelo manages the approved OAuth application and keeps the granted credential encrypted server-side.

Start in Settings → Integrations and check the provider’s current status. This guide describes the configured setup path, not a guarantee of production enablement. Provider approval, plan access and resource permissions still apply.

Snapchat campaign reporting requires an active Growth plan or higher.

Before you connect

  • Create and verify a Snap Business account and organization
  • Create or attach an active ad account
  • Use a Snap account with permission to view that ad account

Connect an existing account

  1. Open the provider in Settings → Integrations for the intended website.
  2. Authorize Obelo from Snapchat's secure consent screen
  3. Choose the ad account Obelo should use for campaign reporting
  4. Return to Obelo and let the first campaign sync complete

If you need a new resource

  1. Create a Snap Business account and organization
  2. Create a developer app and request the required API access
  3. Complete any business verification, compliance, and provider review

Permissions to check

  • The snapchat-marketing-api scope is used to discover permitted ad accounts and read campaign performance
  • Snap controls organization roles and account access; Obelo never receives your Snapchat password

Verify and troubleshoot

Once the organization and ad account are ready, return here to authorize Obelo and choose the account to use.

Snap returned no ad accounts this user can access. Check the signed-in account's organization role and add an active ad account, then reconnect.

Confirm the selected account or resource and inspect the verification or sync result. A saved connection is not proof that an import or publication has completed. Test the intended workflow with an appropriately reviewed item.

Disconnect or change access

Use the provider’s management controls in Obelo to disconnect when supported. Revoke the grant or rotate a dedicated credential at the provider if access must end immediately. Review already-imported data separately; disconnection does not remove content already published elsewhere.

Something unclear or out of date?

Suggest a correction