> 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/apple-search-ads/best-practices.md). # Best Practices ## Recommended setup


Multi-account consolidation	If you manage multiple Apple Search Ads accounts, select all of them in a single data flow and use the Append transformation to combine the data. This is faster than running separate data flows and keeps your reporting in one place.
Separate flows by report type	Create individual data flows for different report types (campaign performance, keyword performance, demographic insights). This makes it easier to schedule them at different times and troubleshoot issues.
Use dynamic date ranges	Instead of manually updating dates each month, use macros like `{{30daysago}}` and `{{yesterday}}` to make your date range dynamic. This keeps your data flows current without manual intervention.
Link to BigQuery for analysis	For large-scale analysis or combining Apple Search Ads data with other sources, export to BigQuery instead of Sheets. This makes joining with other datasets and running complex queries much faster.

## Data refresh and scheduling


Export after campaign day ends	Schedule data flows to run early morning (e.g., 6 AM) so you're always getting complete daily data from the previous day. Avoid pulling data for "today" since metrics are still updating.
Weekly demographic deep-dives	Run demographic/geographic reports weekly instead of daily to reduce API calls and focus on actionable insights. Daily campaign performance reports can be updated more frequently.
Monitor data freshness**	Apple Search Ads data is typically available within 2-4 hours of the reporting period ending. If you need real-time data, run manual checks instead of scheduling frequent automated refreshes.

## Performance optimization


Use "Totals only" when possible	If you don't need daily/weekly/monthly breakdowns, select "Totals only" in the split-by-period setting. This reduces data volume and makes reports easier to read.
Filter by active campaigns	Include only active or recently active campaigns to avoid pulling data for paused campaigns. This reduces noise and makes analysis faster.

## Common pitfalls {% columns %} {% column %} **Do** * Verify the API Account Manager role is assigned before connecting * Test with a manual run and small date range first * Use meaningful names for your data flows (e.g., "Apple Search Ads - Campaign Performance - Weekly") * Schedule flows for early morning to ensure data is finalized * Keep demographic reports separate from performance reports for clarity {% endcolumn %} {% column %} **Don't** * Don't use your main admin account if it lacks API permissions — create a dedicated API user instead * Don't pull data for "today" or the current day — wait until it's finalized the next day * Don't run multiple data flows simultaneously if you have rate limit concerns * Don't mix multiple report types in one data flow if you need different scheduling for each * Don't assume all metrics are available for all campaign types — check Apple Search Ads directly if data seems missing {% endcolumn %} {% endcolumns %} {% hint style="danger" %} **API access requirement:** The API Account Manager role is non-negotiable. If your admin account doesn't have this role, you must either request the role assignment or use a different user account. This is an Apple Search Ads security requirement and Coupler.io cannot work around it. {% endhint %} --- # 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/apple-search-ads/best-practices.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.