> For the complete documentation index, see [llms.txt](https://docs.coupler.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coupler.io/sources/category/ppc/snapchat-ads/faq.md).
# FAQ
What's the difference between "Campaign performance" and "Campaign geo&demography insights"?
"Campaign performance" gives you your core metrics (spend, impressions, clicks, conversions, ROAS, etc.) rolled up by campaign, no segmentation. "Campaign geo\&demography insights" gives you the same metrics, but broken down by a dimension you choose—like age, gender, country, or device OS. So if you have one campaign spending $1,000, campaign performance shows one row. Campaign geo\&demography with "Age" selected shows multiple rows (one per age group) totaling $1,000. Use "Campaign performance" for top-level ROI tracking, and geo\&demography when you want to understand which audience segments are performing best.
Can I combine data from multiple ad accounts in one data flow?
Yes. In the "Ad accounts" step, select all the accounts you want to include. The exported data will have an "account\_id" or "account\_name" column so you can distinguish which rows came from which account. You can then use Coupler's **Append** transformation to combine them in your destination, or keep them as separate tabs/tables and join them in your analytics tool.
Why are my ad or campaign names missing from the performance data?
Snapchat's API sometimes returns IDs without the corresponding names, especially for newly created or renamed ads. **Solution**: Export a "List of Ads" or "List of Campaigns" report (no date range required) and use Coupler's **Join** transformation to add names to your performance data. Join on the campaign\_id or ad\_id field.
For example:
* Flow 1: Campaign performance report → Google Sheets tab "Performance"
* Flow 2: List of Campaigns → Google Sheets tab "Campaigns"
* Use Join in Coupler to match performance data to campaign names on campaign\_id
What attribution window should I use?
It depends on your sales cycle. Recommended starting points:
* **E-commerce with fast checkout**: 1 day post-swipe (user converts immediately)
* **B2B or longer consideration**: 7–28 days post-swipe (includes days for research/decision)
* **Brand awareness or view-through conversions**: Use a post-view window (1 hour, 3 hours, or 1 day) alongside post-swipe
If unsure, start with the default (1 day post-view + 28 days post-swipe). You can always change the attribution window and re-run historical data to compare.
Can I use advanced filters to narrow down my data?
Yes, if the report type supports it (all performance reports and list reports do). You can filter by campaign name, status, objective, or custom properties. The syntax varies—usually you'll see a dropdown to select the field and a text box for the value. Filters reduce the data returned, which can help if you only need a subset of campaigns (e.g., "Active campaigns only").
If you're not sure whether your filter worked, run a manual test and check the output rows to verify.
Why does my data show zero conversions when Snapchat Ads Manager shows conversions?
Check these three things:
1. **Attribution window**: The conversion might fall outside your selected window. For example, if someone converts 2 days after swiping and you've selected "1 day post-swipe," that conversion won't be counted. Try "28 days post-swipe" to match Snapchat Ads Manager's default.
2. **Conversion type**: If you've selected "Web" conversions only and the conversion came from an app, it won't show. Try the "Total" breakdown to see all conversions.
3. **Reporting lag**: Snapchat has a 24
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.coupler.io/sources/category/ppc/snapchat-ads/faq.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.