What is happening?
The Attribution Model is failing because it cannot locate the foundational dataset required to perform its calculations. This acts as a "blocker" for any performance modeling or budget recommendations.
Error: Could not find the source dataset, most likely an access issue. Have a look at the connector errors in the detailed status view.
Why did this happen?
Attribution models do not create raw data; they process data created by your connectors (e.g., GA4, Meta, Google Ads). This error typically occurs when:
Upstream Connector Failure: The connector responsible for creating the dataset has failed to run, meaning the table Alvie is looking for doesn't exist yet.
Dataset Deletion: The BigQuery dataset was manually deleted or renamed in the Google Cloud Console.
Permission Changes: The credentials used by the Attribution Model no longer have "Viewer" or "Owner" access to the BigQuery project where the source data resides.
Incomplete First Run: If you just set up your connectors, the Attribution Model may be trying to run before the connectors have finished their very first data push.
Solution Follow these steps to resolve the issue:
Navigate to Settings: Open the Detailed Status view in your Alvie dashboard.
Locate the Source: Look at the status of your Connectors (e.g., GA4, Google Ads, Meta).
Action: * Fix Red Connectors: If any connectors are showing an error, resolve those first (e.g., refresh credentials or fix billing). The Attribution Model will not work until its "parent" connectors are Healthy (Green).
Wait for Initial Sync: If you just created the connectors, wait until they show as "Finished" before rerunning the Attribution Model.
External Steps: Log in to the Google Cloud Console and ensure the dataset mentioned in your configuration still exists in BigQuery and hasn't been moved to a different project.
Verify: Once all upstream connectors are healthy and the dataset is confirmed, return to the Attribution Model and click Run now. The status should turn Healthy (Green) within a few minutes.
Prevention & Tips To avoid seeing this error again:
IAM Stability: Avoid changing permissions or moving datasets in Google Cloud once the Alvie pipeline is established.
If you encounter any further issues or need additional assistance, please don't hesitate to reach out to the Alvie support team.