You can watch the complete setup process in the video or refer to the step-by-step guide provided below.
This guide walks you through adding an Alvie Attribution model to a Starter Report. This process maps a specific attribution model to a market, which makes Alvie attributed conversion data available directly within your report.
Adding a model introduces a new conversion name, alvie: attribution, into the source_conv_name data column in your base table. This allows you to analyse performance based on the values from your Alvie Attribution models.
After creating or updating a report with Alvie Attribution, you will be able to see the new conversion available on the home page.
Before you begin
To ensure a smooth setup, please verify the following prerequisites. An incorrect setup will prevent you from adding a model and displaying a "Caution" message.
Have an existing attribution model. You must have at least one attribution model created in your workspace. If you don't, you will see a "Note" banner prompting you to create one.
To create a model, navigate to Marketing Evaluation > Attribution and click “Create new model”.
Use the same Google Cloud Project (GCP). The Starter Report and the attribution model must target the exact same Google Cloud Project. This is necessary because the results from both need to be stored in the same BigQuery warehouse to work together.
Use pre-defined Custom Groupings. The report must use Channel and Market Groupings that were created beforehand. Using the "Create a Custom Grouping for this Report only" option is not supported for this feature.
Ensure groupings are valid. You must have at least one Channel Grouping and one Market Grouping added to your report.
Add and Map Your Attribution Model
Follow these steps to add and map your attribution model to the report.
From the Reporting Solutions page, click on the Starter Report you wish to edit, or click Create new report.
Scroll down to the Other Settings section.
Under the Attribution Models heading, click Add attribution models (or Edit if a configuration already exists). An "Add Attribution Models" panel will open on the right.
In the panel, click Select Attribution Model and choose your desired model from the list.
Next, click Select Market and choose the market you want to map this model to. The markets listed are drawn from the Market Groupings you've applied to the report.
Click the Add Model button. The new mapping will appear as a chip under Added Models. You can repeat these steps to add more models.
After you've added all necessary models, close the panel and click Save on the main settings page to apply your changes.
Expected Result
After you save the report, two things happen:
New Conversion Action: A new row value named alvie: attribution is added to the source_conv_name column in your underlying data table.
Report Configuration: This new data, which represents the total attributed conversions for the specific market you configured, is automatically made available for display on the home page or in the Looker Studio dashboard.
Troubleshooting Common Issues
If you encounter issues, refer to the common scenarios below.
Invalid Configuration (Red)
If an added model is highlighted in red, it is invalid, and you will not be able to save the report. This typically happens for two reasons:
Cause: Google Cloud Project Mismatch. The report's target GCP was changed after the attribution model was added.
💡 Solution: You must either change the report's target GCP back to match the one used by the model or remove the invalid model and add a new one that matches the current GCP. You can only remove invalid models; editing is disabled.
Cause: Deleted Market. A market that was mapped to a model was subsequently deleted from the Market Grouping settings.
💡 Solution: Remove the invalid model configuration and re-add it, making sure to map it to a currently existing market.
Configuration Warnings (Orange)
An orange highlight indicates a non-critical warning. You can still save the report, but the configuration may lead to data inconsistencies.
Cause: Channel Grouping Mismatch. The warning appears when the Channel Grouping used in the report differs from the one used in the attribution model. This mismatch can be partial, affecting only some of the data sources in your report (e.g., Google Ads doesn't match, but Google Analytics 4 does).
💡 Solution: To resolve this, ensure that all platforms and data sources in the Starter Report use the exact same Channel Grouping that the attribution model was built with.
Reference: Data Processing Logic
The processing of attribution data depends on the model's last execution status combined with the report's configuration state. The table below outlines the expected behaviour.
Attribution Model Status | Attribution Configuration State | Report Validation Action | Rationale |
Failed | Active or Paused | Processing stops and raises an error. | This is the highest priority. It prevents incomplete or incorrect attribution data from being included in the report. |
Not run yet | Active or Paused | Excludes attribution data from the report. | This ensures the report only processes data from a model that has successfully run at least once. |
OK | Active or Paused | Processing proceeds normally. | The report processes and displays the latest available attributed data. |
Running / Queued | Active or Paused | Processing proceeds normally but with empty output tables for attribution results. | The report runs but excludes attribution from processing. When the report is re-ran and attribution model processing is finished, then data will be included. |