You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Adstock decay value typically represents the percentage of ad’s impact that remains over time. It accounts for lagged effect (carryover), which is the delayed impact of advertising on sales. To answer your questions:
Adstock decay rate can be used to explain how the target KPI is being impacted by current ad-spend in a subsequent (future) time period. This can help devise marketing strategies along with information from the Hill function which gives the amount of incremental increase in returns for each additional unit of ad-spend. This information can be used to devise how to allocate marketing investments.
If a particular media channel has an adstock value of 0.55 at a point in time, this means that the impact of the spend on that channel diminishes to 55% of the initial impact in the subsequent time period. As an example for easier understanding, if the initial impact at a particular point in time is 100 units and the adstock decay is 0.55, then in the next period the estimated impact would be 55 units.
Meridian doesn’t allow assigning individual lag values to each media channel. The max_lag parameter captures the maximum value of lag present in all channels. If a particular channel has a lower carryover effect and thus lower lag value, the model will simply train and assign the coefficients accordingly so that this is captured. Setting max_lag value as the maximum possible lag for all channels is the recommended approach. You may check our documentation on Setting the max_lag Parameter for more information regarding this.
Additionally, you may use the plot_adstock_decay() method if you wish to visualize the evolution of adstock decay rate over time (Ref - Adstock Decay).
Feel free to reach out for any further queries regarding this.
We tried checking for the adstock decay rate for our model with max lag of 6. Here are the results for few of our channels (see table below):
We have following queries around it
The text was updated successfully, but these errors were encountered: