Destination
Snapchat Ads
Create a Snapchat Ads Destination
-
Click the + icon on the Nexset that will be sent to the Snapchat Ads destination, and select the Send to Destination option from the menu.
-
Select the Snapchat Ads connector from the list of available destination connectors. Then, select the credential that will be used to connect to your Snapchat Ads account, and click Next; or, create a new Snapchat Ads credential for use in this flow.
-
In Nexla, Snapchat Ads destinations can be created using pre-built endpoint templates, which expedite destination setup for common Snapchat Ads endpoints. Each template is designed specifically for the corresponding Snapchat Ads endpoint, making destination configuration easy and efficient.
• To configure this destination using a template, follow the instructions in Configure Using a Template.Snapchat Ads destinations can also be configured manually, allowing you to send data to Snapchat Ads endpoints not included in the pre-built templates or apply further customizations to exactly suit your needs.
• To configure this destination manually, follow the instructions in Configure Manually.
Configure Using a Template
Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common Snapchat Ads endpoints. Each template is designed specifically for the corresponding Snapchat Ads endpoint, making destination setup easy and efficient.
-
To configure this destination using a template, select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.
Configure Manually
Snapchat Ads destinations can be manually configured to send data to any valid Snapchat Ads API endpoint. Manual configuration provides maximum flexibility for accessing endpoints not covered by pre-built templates or when you need custom API configurations.
Using manual configuration, you can also configure Nexla to automatically send the response received from the Snapchat Ads API after each call to a new Nexla webhook data source.
API Method
-
To manually configure this destination, select the Advanced tab at the top of the configuration screen.
-
Select the API method that will be used for calls to the Snapchat Ads API from the Method pulldown menu. Snapchat Ads API typically uses POST method for creating resources.
Data Format
- Select the format in which the Nexset data will be sent to the Snapchat Ads API from the Content Format pulldown menu. Snapchat Ads API expects JSON format for all requests.
API Endpoint URL
- Enter the URL of the Snapchat Ads API endpoint to which data will be sent in the URL field. This should be the complete URL to your Snapchat Ads endpoint (e.g.,
https://adsapi.snapchat.com/v1/adaccounts/{ad_account_id}/campaigns). Include any required path parameters in the URL.
Ensure the API endpoint URL is correct and accessible with your current credentials. The Snapchat Ads API endpoint URL should include the API base URL (https://adsapi.snapchat.com/v1/) and point to the endpoint where you want to create resources. The endpoint URL should include the appropriate path parameters (e.g., ad account ID). You can test the endpoint using the Test button after configuring the URL.
Request Body
- Configure the request body that will be sent to the Snapchat Ads API. The request body should contain the resource data formatted as JSON, with field names matching the Snapchat Marketing API's expected structure. The request body format is typically
{message.json}to send the entire Nexset data as JSON, or you can construct a custom JSON structure with specific field mappings.
The request body must be valid JSON and must match the Snapchat Marketing API's expected format for the specific resource you're creating (campaigns, ads, etc.). Snapchat Marketing API uses specific structures for different resources. For detailed information about request body formats, available endpoints, and resource structures, see the Snapchat Marketing API documentation.
Save the Destination
- Once all of the relevant steps in the above sections have been completed, click the Next button to proceed with the rest of the data flow configuration, or click Save to save the destination configuration for later use.