CTA
Botones, banners, ventanas emergentes y paneles deslizantes que los visitantes ven en una página o app y usan, segmentados por página, audiencia y momento, con variantes e informes.
The CTA list
CTAs sit under Engage. Each row is one CTA with its kind, its status (draft, live or paused), its views, clicks and click rate over the last 30 days, and when it was last edited; the head counts the live CTAs against the plan. New CTA names a CTA and picks its kind: a pop-up in the middle of the screen, a banner across the top or bottom, a slide-in from a bottom corner, or a block embedded in the page.
Building a CTA
Build holds three panes: the kind, its placement and the variants on the left, the chosen variant on a sketch of a page in the middle, and that variant’s heading, body, image, up to two buttons and colours on the right. A button opens an https address, opens one of the project’s forms in place, starts a messenger conversation or closes the CTA. Each colour pair shows its measured contrast, and a pair under 4.5:1 is refused. Adding a variant makes the CTA a test: the variants split the visitors by shares that add up to 100, and each visitor keeps the variant they were first shown.
Targeting sets the pages it shows on (an address that equals, contains, starts with or matches a pattern with *, and pages left out), the audience (everyone, known people or anonymous visitors), the devices and page languages, conditions on the visitor’s properties or cohorts, and a flag it follows. When sets what opens it (the page opening, a delay, a scroll depth, exit intent or a click on an element), how often it shows (once, once per visit, or again after some days), its schedule, and a goal event: a click followed within 24 hours by that event, or by the submission of a form the CTA opened, counts as a conversion. In an app a CTA shows on open or after its delay.
Edits stay a draft until Publish, so a visitor never sees a CTA change between two pages. Publishing a CTA that is not live takes one of the plan’s live places; Pause takes it off every page and frees its place, and Resume shows the same version again.
Placing it
Install opens a side panel with the script a site loads once on every page, <script src="…/ctas.js" data-key="…">, the slot an embedded CTA is drawn into, <div data-prodantix-cta="…">, and the Flutter widget an app wraps a screen in, ProdantixCtas, with ProdantixCtaSlot for an embedded CTA. The web SDK’s startCtas(client) does the same for a site that already loads the SDK.
The report
Report shows each variant’s views, clicks, click rate, conversions, conversion rate and dismissals over the last 30 days, which variant leads on clicks and on conversions and whether its lead holds at 95% confidence (a two-proportion test), and views and clicks by day. CTAs come with Growth and up, a second variant with Scale and up, and the live CTAs a company keeps are 10, 50 or unlimited; the "Powered by Prodantix" line leaves the CTA on Enterprise. The phone lists each CTA with its numbers.
Where this meets the API
On GraphQL the list is crmCtas, crmCta reads one, crmCtaReport reads its report and crmCtaTotals every CTA's numbers; writing is createCrmCta, updateCrmCta, publishCrmCta, pauseCrmCta, resumeCrmCta and archiveCrmCta, and every change arrives on the crmCtaChanges subscription (GraphQL reference). REST serves the same under /v1/projects/{projectId}/ctas, and the MCP tools are prodantix.ctas.list, prodantix.ctas.get, prodantix.ctas.report, prodantix.ctas.totals, prodantix.ctas.create, prodantix.ctas.update, prodantix.ctas.publish, prodantix.ctas.pause, prodantix.ctas.resume and prodantix.ctas.archive. A visitor's browser or app reads the CTAs a page may show from /v1/ctas on the edge, which sends only the visitor's own variant.