Start campaigns (v3)

Deprecated: use experience.campaigns.start.v4 (experience_campaigns_start_v4), which also takes stores picked on Google Maps (locationContexts) and then may answer before the campaign commits (delivery setting_up_stores); without them it starts exactly as v4, naming the same campaign for the same Idempotency-Key. Start an always-on Experience campaign over chosen customers (or, with follows, a share of a Discovery campaign's customers, as Bootup's Experience chooses them, which the campaign records and re-reads each run: a customer who left that campaign leaves, and a store its customers no longer cover lends its share, up to 100; while that campaign is archived its customers stay as they are until it is restored, and once it is deleted, for good; or, with locationKeys, every customer at chosen stores of the business profile, dealt one per store until 100, chosen once at the launch) and pages (or one connected app version on one mobile device), on chosen devices, shopped by chosen agents: Point11's own shopper unless agents names others, each of which runs its vendor's model in Point11's browser and shops every customer on every page and device as its own visit. It shops its whole grid now. Once that first run is accepted, a prorated share of its customers shops again across the rest of the UTC month, then every customer shops once each UTC month, placed on the business's published hours. A first run in which no visit delivered starts no monthly runs. Name competitorSourceCampaignId, a Discovery campaign on the same business profile, and every run also shops each customer's direct competitors: every brand that customer's latest settled conversation there labelled a direct competitor, read again each run, with no cap; a customer with none shops the pages alone. Subscribes nothing; each run uses the organization's existing allowance (and pay-as-you-go, if the organization turned it on). Returns the campaign and its launch entry; runs dispatch shortly after.