In order to manage campaigns and ads in Snapchat, Smartly.io needs access to those assets via Snapchat user authentication. Permission for Smartly.io to use the authentication needs to be given separately for ad accounts and for catalogs.
To manage permissions for Snapchat ad accounts and catalogs:
- In the top toolbar, click Accounts.
- Next to a Snapchat account, click … > Accounts Settings.
Ad account permissions
Account Authorizer is visible under the Account Settings page:
Ad account authentication can be reconnected or changed by clicking the Reconnect button. This can be relevant if, ad account authorizer's password is updated in Snapchat, if the authorizer no longer has access to the ad account, or if the authorizer should be changed to another person.
In order to be able to create Dynamic Ads campaigns, the catalogs needs to be connected to Smartly.io.
In Snapchat catalogs belong to an Organization. Please note that user connecting the catalog will need Organization Admin rights for the Organization that owns the catalog. The Business Admin role is not sufficient enough for connecting a catalog.
Connected catalogs are visible under Account Setting > Catalog Permissions:
Connect a new Snapchat catalog
Under 'Catalog Permissions' page there is button to 'Connect Catalogs For Account'
Clicking 'Connect Catalogs For Account' button will open a new pop up window to add new catalogs:
Clicking button 'Continue' will open dialog for choosing catalogs to add:
Choose needed catalogs and click 'Enable catalogs'
Once the catalogs are enabled they are ready to be used for Dynamic Ads campaigns.
I can't see any catalogs in the catalog listing view. / I get an error in the catalog listing view.
First make sure you have the needed permissions. You'll need to have either Organization admin rights (gives access to all catalogs under the Organization), or Catalog admin or Catalog Advertiser role to a specific catalog.
There is currently also an edge case, that leads to catalogs listing to fail loading. This is when user has Business admin rights, but no Organization admin rights. In these cases, either give Organization admin rights to user or remove the Business admin rights. We are working to solve the issue on supporting this combination of permissions correctly.