Acquisition agentManaged
Set the yield you want. We find the wall that earns it.
The Acquisition agent tests the meters, walls, offers and prices you deployed against a holdout on your current rules, and moves traffic toward whatever earns your goal. Anything new waits for your deploy.
Managed today: EdgeKit’s team runs each agent’s loop with you. You approve and deploy every change, and automation takes over each step as it ships.The managed service
Acquisition agent · one loopIllustrative
- Goal
- Yield per 1,000 readers
- Guardrails
- Price floor £4Discount ≤ 50%Page views ≥ 3 / readerExploration ≤ 20%
Share of traffic
- Meter of 5, then offer30%
- Registration wall at 330%
- Trial offer at 230%
- Holdout · your current rules10%
ProposalAdd an annual offer at the trial pointWaiting for your deploy
You set the goal: yield per 1,000 readers.
What you set
You pick the goal and write the limits
Goals
- Yield per 1,000 readersDefault
- Subscription starts
- Registrations
Guardrails
- A price floor and a deepest discount
- A floor on page views per reader, so ad impressions hold
- A floor on registration rate
- At most one prompt per reader per visit
- Protected readers and stories: subscribers, seat holders, anything you tag public-interest
- An exploration cap: how much traffic may try an unproven arm
- A stop-loss against your holdout
What it does
Nothing new goes live without your deploy
Moving traffic between the arms you approved is the agent’s job, and today EdgeKit’s team does it. Anything new is a proposal in your console, and approving it is a deploy.
Decides inside what you deployed
- Which of your deployed walls, offers and prices each reader is tested on
- How much traffic each arm gets: our team moves it toward the arm that earns your goal
- Moving traffic back to your holdout when the stop-loss is hit
Proposes for your deploy
- A new offer, price point or trial length
- A new rule or a new segment
- Retiring an arm that keeps losing
Never does
- Changes a price, an offer or a rule without your deploy
- Puts a wall in front of a subscriber or a protected story
- Learns from another organization’s readers
Coming soon Soon
- Traffic moved request by request, without waiting for the team
- A stop-loss that trips on its own
- An arm picked per reader, not per segment