A plain-language overview of the access we'll request, what it lets us do, who on your team should connect, and what to expect during setup.
What to expect
Connecting takes a couple of minutes. When you connect Snapchat Ads in Medialake, you're redirected to the official Snapchat sign-in page, then to Snapchat's consent screen describing the access being requested. You approve it yourself and can revoke access at any time. We never see or store your password: the login happens entirely on snapchat.com, and once you approve you're returned to Medialake.
Medialake is a reporting and media platform. We never create, edit, pause, or spend anything in your ad accounts. Every request the connector makes to Snapchat's official Marketing API is a read.
You Medialake Snapchat │ connect source │ │ │────────────────────────▶│ │ │ redirect to Snapchat │ │ │◀────────────────────────│ │ │ log in & grant access │ │ │──────────────────────────────────────────────────▶│ │ redirect with code │ │ │◀──────────────────────────────────────────────────│ │ │ exchange code │ │ │────────────────────────▶│ │ │ access + refresh token │ │ │◀────────────────────────│ │ source authorized │ │ │◀────────────────────────│ │ │ │ renews automatically │ │ │────────────────────────▶│
Two ways to connect
Snapchat Ads can be connected through Medialake's OAuth app or through your own OAuth app:
Medialake's OAuth app (default). Accounts connect using Medialake's central Snapchat Ads app. No setup is required: just sign in and approve.
Your own OAuth app (optional). If your organization would rather own the app that appears on Snapchat's consent screen, you can create an OAuth app in your own Snapchat Business Manager and add its credentials to Medialake. Your organization owns the app and can disable it at any time.
The access requested, and everything else on this page, is identical for both options.
Setting up your own OAuth app (optional)
Most accounts connect with Medialake's OAuth app and can skip this section. To create your own app you need to be an Organization Admin in Snapchat Business Manager; the OAuth Apps section is only visible to admins.
Sign in to Snapchat Business Manager as an Organization Admin.
Open your organization's Business Details and find the OAuth Apps section.
Create a new OAuth app. Give it a name your team will recognize, because this is the name shown on Snapchat's consent screen.
Set the redirect URI to exactly:
https://oauth2.medialakeapp.com/snapchatads-redirect
Save the app and copy its Client ID and Client Secret.
>Keep the Client Secret private. Store it in an approved password manager or secret-management system. Do not email it, paste it into a support ticket, or commit it to source control.
Add your app's credentials to Medialake
You need Medialake administrator privileges for this step.
Open Administration → Integrations from the sidebar.
Open the Snapchat Ads integration.
In the Access Keys section, click Create New Setting.
In the New access key panel, give the key a Name, for example
Marketing Snapchat Ads app. Team members see this name when they choose an app to connect with.Under Credentials, fill in both fields:
- Enter your Snapchatads Client ID here without any space: the Client ID from step 5 above.
- Enter your Snapchatads Client Secret here without any space: the Client Secret from step 5 above.
Under Who can use it?, choose which teams can connect accounts with this key, or allow all teams.
Click Save access key.
Medialake rejects either value if it contains a space. The values are stored encrypted and are never shown again.
Connect and choose what to sync
Any team member who is allowed to connect sources can do this.
Open Connections → Catalogue from the side menu.
Find Snapchat Ads and click Connect.
Under How do you want to connect?, choose Connect it myself: "Sign in with your Snapchat Ads account and approve what Medialake can access."
If your organization has saved its own OAuth app as an access key, an OAuth app dropdown also appears. Leave it on Medialake's OAuth app (tagged Recommended), or pick your organization's app by the name it was saved under.
Sign in to Snapchat and approve the request. You're returned to Medialake.
Choose what to sync. Medialake lists the organizations the connecting user belongs to; open an organization to see its ad accounts. You can select:
- A whole organization. This syncs every ad account in it. The organization's ad accounts are looked up again on each sync, so ad accounts added to the organization later are picked up automatically.
- Individual ad accounts.
For each selected ad account, Medialake syncs:
Media Library images and videos that have a READY status. Media that is still uploading, and other media types such as interactive playable assets, are skipped.
Campaign structure: campaigns, ad squads, ads, and creatives, so each media file can be linked to the ads that use it.
Daily performance: impressions, swipes, spend, video views and quartiles, view completions, screen time, reach (uniques), frequency, shares, and saves.
Verifying it's really us
On Snapchat's consent screen, check that the app requesting access is the one you expect: Medialake's Snapchat Ads app, or the app your organization created and named. If the name doesn't match, stop and contact us. Never approve a Snapchat access request you weren't expecting.
Who should do the connecting
The connection is tied to the Snapchat account that signs in. Have it done by someone who:
Is a member of your Snapchat organization and of each ad account you want to sync. Snapchat only returns performance stats to members whose ad account role includes reporting access. Snapchat's Marketing API FAQ names the reports role for this, which Business Manager calls Data Manager, so check their role if you want performance data.
Is a permanent member of your team, or uses a dedicated account your company maintains. Snapchat's refresh token stops working once the user it belongs to loses access, so if the person who authorized us leaves or is removed from the organization, someone else will need to reconnect.
Their Snapchat login is used only to authorize the connection. The only account details we read are the user's ID, display name (or username), and email, to confirm who authorized.
Limiting what Medialake can access
We inherit exactly the connecting person's access, enforced by Snapchat on every request. To keep the connection as narrow as possible, have someone whose membership covers only the organizations and ad accounts in scope do the connecting. Ad accounts outside their access are invisible to us.
The permission we request
Permission (scope) | What it lets us do | How we use it |
| Use Snapchat's Marketing API on behalf of the connecting user: organizations, ad accounts, Media Library, campaigns, ad squads, ads, creatives, and performance stats. | READ ONLY: the connector only sends read requests |
That's the only scope we request. Snapchat's other scopes, for the Conversions API and the Public Profile API, are not requested.
Snapchat does not offer a separate read-only scope for the Marketing API, so this one scope is not limited to reading on Snapchat's side. Two things keep the connection read-only in practice: the connector itself never sends a request that changes anything, and the connecting member's role caps what any request could do.
What Medialake can and cannot do
Medialake can:
List the organizations and ad accounts the connecting user can access
Read Media Library images and videos, including their names, sizes, and download links
Read campaigns, ad squads, ads, creatives, and performance stats
Medialake does not, and cannot:
See or store your password, or log in as you
Reach any organization or ad account the connecting user cannot access
The connector never:
Creates, edits, pauses, or deletes campaigns, ad squads, ads, creatives, or media
Changes budgets or billing, or spends money on your account
Adds, removes, or manages members of your organization
Staying connected
Snapchat access tokens are short-lived: they expire after an hour. When you connect, Snapchat also issues a refresh token. When Snapchat turns down an expired access token, Medialake uses the refresh token to get a new one and retries the request, all in the background, so there's nothing to re-approve on a schedule.
Snapchat's refresh token does not expire on its own, but it stops working if the connecting user's access is removed. If Snapchat refuses to renew the connection, Medialake stops syncing the source until someone connects it again from Connections → Catalogue.
If your organization uses its own OAuth app and its Client Secret changes, save the new values as an access key in Medialake and reconnect.
Revoking access
You're in control at any time. To remove the connection:
On Snapchat, signed in as the connecting user, go to accounts.snapchat.com, open the list of apps connected to the account, and remove the app, or
Have an Organization Admin remove the connecting user's access to the organization or ad accounts in Business Manager, or
Disconnect the Snapchat Ads source in Medialake.
Once access is revoked on Snapchat's side, the tokens stop working and data collection stops. No action is needed on our side.
Troubleshooting
Symptom | What to check |
The access key won't save | Both values are required and cannot contain spaces. Paste them again without leading or trailing spaces. |
Snapchat shows a redirect URI error (own OAuth app) | The redirect URI on your OAuth app must be exactly |
"This connection link is invalid or has expired. Please start the connection again." | The sign-in page was left open too long, or the link was already used. Start again from Connections → Catalogue. |
No organizations are listed after connecting | The Snapchat account that signed in is not a member of any organization. Reconnect with an account that is. |
An ad account is missing from an organization | The connecting user is not a member of that ad account. Add them in Business Manager, then reopen the selection. |
Some media didn't sync | Only images and videos with a READY status are synced. Media that is still processing is picked up on a later sync once Snapchat marks it ready. Other media types are skipped. |
Media syncs but performance data is missing | The connecting user's ad account role may not include reporting access. Ask an Organization Admin to check the role. |
A working connection stopped syncing | The connecting user lost access, the app was removed from their Snapchat account, or (own OAuth app) the Client Secret changed. Reconnect, and update the access key if the secret changed. |
If you get stuck, contact [email protected]. Do not include your Client Secret.
Further reading (Snapchat documentation)
Marketing API authentication: OAuth apps, scopes, and the authorization-code flow used to connect
Marketing API FAQ: token lifetimes, revoking app access, and the roles needed for reporting
Snapchat Business Manager: managing your organization, members, and ad accounts
You can review or withdraw access at any time from your Snapchat account's connected apps.
