> 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/quora-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>Match dimension to your reporting goal</strong></td><td>Use Account-level for budget overviews, Campaign for strategy analysis, Ad for creative testing. Pulling Ad-level data when you only need campaign totals creates unnecessarily large datasets.</td></tr><tr><td><strong>Use daily splits for trend analysis only</strong></td><td>If you just need period totals (e.g., monthly spend), leave the split set to "Totals only." Daily splits multiply row count significantly and slow down refreshes for long date ranges.</td></tr><tr><td><strong>Combine entities in one data flow</strong></td><td>Add both Ad analytics and List of recently collected leads as separate sources in a single data flow. Use the Append or Join transformation to analyze lead volume alongside ad spend in one report.</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>Refresh leads frequently</strong></td><td>Because the leads entity only returns recently collected leads, set up a daily (or more frequent) schedule with Append mode in your destination. This builds a cumulative lead log over time without losing older submissions.</td></tr><tr><td><strong>Use completed periods for stable numbers</strong></td><td>Quora Ads can update conversion data retroactively. For reporting that needs to reconcile with Quora's UI, pull Last Month or a completed custom range rather than in-progress periods like This Month or Last 7 Days.</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>Break large historical loads into chunks</strong></td><td>Pulling All Time at the Ad + Daily level for large accounts can time out. Use Custom date ranges to pull data quarter by quarter, then Append the results into a single destination table.</td></tr><tr><td><strong>Filter to specific campaigns or ad sets when possible</strong></td><td>If you only care about a subset of campaigns, use the campaign or ad set filter parameters. This reduces query size and speeds up sync time, especially for daily splits.</td></tr></tbody></table>

## Common pitfalls

{% hint style="danger" %}
**Don't rely on a one-time pull for lead data.** The leads entity has a recency limitation in Quora's API. If you pull leads once and don't set up a recurring schedule, you will lose older lead records that fall outside the API's lookback window.
{% endhint %}

{% columns %}
{% column %}
**Do**

* Set up Append mode for the leads entity to accumulate data over time
* Use the Custom period with specific dates when reconciling historical data against Quora's UI
* Pull ad-level data for creative analysis; use account or campaign level for budget reporting
* Test with a short date range first before running a large historical load
  {% endcolumn %}

{% column %}
**Don't**

* Use "All time" with daily splits at the ad level on large accounts without first narrowing scope
* Compare Coupler.io data to the Quora UI mid-period — attribution windows are still open
* Pull ad-level daily data when your report only needs campaign or account totals
* Forget to check the dimension setting — a mismatch is the most common cause of number discrepancies
  {% 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/quora-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.