Experiment

  • Google Ads experiments allow users to test changes on multiple campaigns and compare performance.

  • Effective changes can be applied to campaigns after testing.

  • Experiments have various fields including name, description, type, status, and date range.

  • Experiment status and promotion status are output only fields.

  • Base campaign changes can be synced to trial campaigns if sync is enabled during creation.

A Google ads experiment for users to experiment changes on multiple campaigns, compare the performance, and apply the effective changes.

Proto definition

Fields

description

string

The description of the experiment. It must have a minimum length of 1 and maximum length of 2048.

end_date

string

Date when the experiment ends. By default, the experiment ends on the campaign's end date. If this field is set, then the experiment ends at the end of the specified date in the customer's time zone.

Format: YYYY-MM-DD Example: 2019-04-18

experiment_id

int64

Output only. The ID of the experiment. Read only.

goals[]

MetricGoal

The goals of this experiment.

long_running_operation

string

Output only. The resource name of the long-running operation that can be used to poll for completion of experiment schedule or promote. The most recent long running operation is returned.

name

string

Required. The name of the experiment. It must have a minimum length of 1 and maximum length of 1024. It must be unique under a customer.

promote_status

AsyncActionStatus

Output only. The status of the experiment promotion process.

resource_name

string

Immutable. The resource name of the experiment. Experiment resource names have the form:

customers/{customer_id}/experiments/{experiment_id}

start_date

string

Date when the experiment starts. By default, the experiment starts now or on the campaign's start date, whichever is later. If this field is set, then the experiment starts at the beginning of the specified date in the customer's time zone.

Format: YYYY-MM-DD Example: 2019-03-14

status

ExperimentStatus

The Advertiser-chosen status of this experiment.

suffix

string

For system managed experiments, the advertiser must provide a suffix during construction, in the setup stage before moving to initiated. The suffix will be appended to the in-design and experiment campaign names so that the name is base campaign name + suffix.

sync_enabled

bool

Immutable. Set to true if changes to base campaigns should be synced to the trial campaigns. Any changes made directly to trial campaigns will be preserved. This field can only be set when the experiment is being created.

type

ExperimentType

Required. The product/feature that uses this experiment.