Import and sync

Admetriva does not query Google or Meta every time a page is opened. Data is imported in the background and stored locally, by day. That is why pages load quickly, and the figures change only after a sync.

The initial import

The initial import starts automatically, only once, when you save the project's Google accounts. Saving the accounts again does not duplicate it.

• The default period starts on January 1, 2025 and ends today, in the project's time zone. The start date may be different if it was configured otherwise for your project.
• Google Ads provides history for the requested period, within the limits of the account and its permissions.
• Merchant Center and the Meta catalog only provide today's state. Their history starts at the first sync.

The import runs in monthly chunks, one after another. You can close the page: the import continues.

The “Data import” page

The page shows the current operation, the stage, the dataset and month being imported, the progress for each dataset, and the skipped datasets, each with its reason. A skipped dataset is not an error: for example, Meta product data is skipped as long as you have not chosen a catalog.

The available actions:

• Retry the failed chunks.
• Cancel: the chunk in progress finishes, the rest stop. The data already imported stays.
• Repair data gaps: imports only the missing days.
• Extend history: imports earlier years or a range you choose. Only what is missing is imported; complete periods are not re-imported.

Automatic sync

After a successful initial import, or a partially successful one, automatic sync starts on its own. It brings in the new days and re-imports the most recent days, because Google and Meta can report conversions late. How often it runs depends on the workspace's plan and the project's settings.

Each dataset has its own pace: campaign performance updates often, search terms once a day, the catalog every few hours. That is why one dataset can be “behind” without the rest of the report being affected.

Pause after repeated errors

If a dataset fails several times in a row, its sync is paused for a while and then resumes on its own. The pause and the last error are shown in the “Data status” band and in Data and synchronization. See How to read the data status.