> 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/reddit-ads/best-practices.md).

# Best Practices

## Recommended setup

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th></tr></thead><tbody><tr><td><strong>Start with Campaign performance (daily)</strong></td><td>This entity gives you the most actionable data — daily spend, impressions, clicks, and conversions. Use it as your primary source and join it with the Campaigns entity to enrich performance rows with budget and objective context.</td></tr><tr><td><strong>List all ad accounts explicitly</strong></td><td>Coupler.io won't auto-discover your Reddit Ads accounts. Add every account ID you want to track in the Ad accounts field upfront — this avoids silent gaps in your data when you run reports across accounts.</td></tr><tr><td><strong>Use Append to consolidate multiple accounts</strong></td><td>If you manage several Reddit Ads accounts, add each as a separate source in one data flow and use the Append transformation. This gives you a single unified table across all accounts without manual merging.</td></tr></tbody></table>

## Data refresh and scheduling

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th></tr></thead><tbody><tr><td><strong>Account for the 24-hour reporting delay</strong></td><td>Reddit Ads data for the most recent day is often incomplete. If you're tracking daily performance, schedule your refresh for early morning so the previous day's data has had time to finalize before it's pulled.</td></tr><tr><td><strong>Set a rolling date range for ongoing monitoring</strong></td><td>For regular performance monitoring, set your start date to a fixed point (like the campaign launch date) and update the end date periodically. Avoid pulling excessively long ranges in one go — shorter windows are faster and less likely to hit rate limits.</td></tr></tbody></table>

## Performance optimization

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th></tr></thead><tbody><tr><td><strong>Join Campaigns with daily performance data</strong></td><td>The Campaigns entity contains budget and objective fields that the performance report doesn't include. Use a Join transformation on Campaign ID to get a complete picture — spend vs. budget, performance vs. objective — in one output table.</td></tr><tr><td><strong>Send data to AI tools for instant analysis</strong></td><td>Route your Campaign performance (daily) data to ChatGPT, Claude, or Gemini as a destination. This is useful for generating narrative performance summaries or surfacing anomalies without building a full dashboard.</td></tr></tbody></table>

## Common pitfalls

{% hint style="danger" %}
Don't rely on the Campaigns, Ad groups, or Ads entities for historical data — they return a current snapshot only. If a campaign was paused or an ad was deleted, it may not appear. Always use Campaign performance (daily) with a date range for historical analysis.
{% endhint %}

{% columns %}
{% column %}

### Do

* Specify all ad account IDs you need before running the data flow
* Use shorter date ranges (1-3 months) for daily performance pulls
* Join performance data with campaign metadata for richer reports
* Wait for recent days to finalize before treating them as complete
  {% endcolumn %}

{% column %}

### Don't

* Assume Coupler.io will auto-discover your ad accounts
* Pull multi-year date ranges in a single request — it can time out
* Compare same-day Reddit Ads data as final — it often updates retroactively
* Use a single API key shared across teams without confirming it has access to all required accounts
  {% endcolumn %}
  {% endcolumns %}


---

# 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/reddit-ads/best-practices.md?ask=<question>&goal=<endgoal>
```

`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.