audiences_for_shopper
ChatGPTList the audiences a given shopper currently belongs to. Takes the shopper's profile id.
confirm_lead_move
ChatGPTApply one previewed move. Takes the preview_id and the declaration exactly as preview_lead_move returned it. Refused, with nothing moved, if the declaration differs, the preview expired, the move limit is exceeded, or any lead or the target stage changed since the preview. One confirmation moves one batch. Events are sent only to ad accounts the store has connected, and only when the target stage is set to send conversions and the move is not quiet; the declaration names every platform that will receive one. The result says how the leads moved and until when they can be undone.
confirm_lead_undo
ChatGPTApply a previewed undo. Takes the preview_id and the declaration exactly as preview_lead_undo returned it. The result says what moved back.
create_compliant_page
ChatGPTStep 1 of store setup. Create a compliant page with the same fields as the console's new page form. If the store already has a Meta pixel, creating the page also creates a route for it. Then call get_compliant_page_dns_setup for the records the merchant must add. Without declaration it returns a preview and the declaration for this change, and changes nothing. With the same arguments and that declaration it applies the change and returns how to undo it.
create_pixel
ChatGPTStep 2 of store setup. Add a Meta pixel by label and pixel ID. The access token is never sent through this tool: the result carries a credential link, valid for a limited time, where the merchant enters the token themselves. Zappush doesn't email the link; give it to the user for the merchant. The pixel sends nothing until the token is in. Without declaration it returns a preview and the declaration for this change, and changes nothing. With the same arguments and that declaration it applies the change and returns how to undo it.
create_pixel_credential_link
ChatGPTMake a new credential link for a Meta pixel, where the merchant enters or replaces its pixel ID and access token. Any earlier link for the pixel stops working. Zappush doesn't email the link; give it to the user for the merchant.
create_route
ChatGPTStep 3 of store setup. Create a route: it needs a compliant page and a Meta pixel from the same store. A route is created with a compliant page only when the store already had a Meta pixel, so check list_routes first and update that route if there is one. Takes the same fields as the console's new route form. Without declaration it returns a preview and the declaration for this change, and changes nothing. With the same arguments and that declaration it applies the change and returns how to undo it.
describe_lead_pipeline
ChatGPTDescribes the store's lead pipeline: every stage in board order with its colour, category and whether new leads land there; the event that moves leads into it, when that event last fired and how often this week; what each stage sends to each connected destination (Meta, Google Ads, Google Ads Data Manager, TikTok, Snapchat, Pinterest, Reddit, LinkedIn, X, Microsoft, Quora, OpenAI and GA4, whichever are connected) and whether it is sending, configured but not currently sending, off, or couldn't be read; which quick actions target it; whether Meta stage events are switched off; and this session's Move quietly and move limit. Other lead tools take stage names exactly as this returns them.
find_leads
ChatGPTFind leads and save them as a selection that can be reviewed and later moved. All criteria are combined with AND: stages (names from describe_lead_pipeline), created or created_or_converted day ranges (store timezone), channels, campaigns, form and landing pages, country, not contacted, going cold, behaviour (has or has never fired an exact event name, optionally within N days) and an exact list of emails or names. Returns a selection_id, the exact count, reasons grouped with counts, a sample of up to 10 leads, and a CSV link valid for 1 hour. Leads with no linked visitor are left out of a has-never-fired search unless behaviour.include_no_visitor is true; a group says how many leads fired a variant of the event. A selection lasts 24 hours and never changes.
get_compliant_page_dns_setup
ChatGPTThe DNS records the merchant must add for a compliant page's domain, as the console's DNS setup panel shows them.
get_custom_store_script
ChatGPTRead the custom JavaScript on a store using Standard delivery, as the console's Settings, Install card shows it: the source, its note, when it was last compiled and who last changed it. On a store that can't have one it answers available false with the reason.
get_lead_selection
ChatGPTShow a saved selection again: its count, grouped reasons, a sample of up to 10 leads, and a fresh CSV link valid for 1 hour.
get_lead_session_settings
ChatGPTRead this session's lead pipeline settings: whether Move quietly is on (moves send nothing to any destination: Meta, Google Ads, TikTok or any other connected platform) and the move limit (most leads one move may touch). Both reset when the session ends.
get_route_custom_scripts
ChatGPTZappush support only. Read all four script fields of one route: the store page and compliant page add-on blocks (source, note, last compiled, and the earlier version if there is one), the two full replacement scripts as raw text, and a served flag per field saying whether it reaches a page today.
list_audiences
ChatGPTList the saved audiences for a store, with the current member count of each. Use list_stores first to resolve a store name to a store_id.
list_compliant_pages
ChatGPTStep 1 of store setup. List the store's compliant pages as the console shows them: domain, whether the domain is verified and live, page text and colours, and whether the page is active.
list_pixels
ChatGPTStep 2 of store setup. List the store's Meta pixels as the console shows them: label, pixel ID, masked token, status, whether sending is on, the last error, and whether the pixel still needs a route.
list_routes
ChatGPTStep 3 of store setup. List a store's routes as the console shows them under Routes: label, compliant page, destination URL, Meta pixel and extra pixels, status, whether it's the default, and setup blockers that stop it sending events.
list_stores
ChatGPTList all stores you have access to. Returns store name, ID, and platform. Use this to resolve a store name to a store_id before calling query_data.
preview_lead_move
ChatGPTPreview moving a selection (from find_leads) to one stage. declared_effect is required: the target stage and delivery, send or quiet, with no default. Returns the exact count, leads left out, a risk entry for every connected destination the stage's conversions reach, Meta, Google Ads and each other platform such as TikTok (would send, already sent, already sent Lead from the browser, no contact, not sending), a quiet recommendation when sending would duplicate, whether the move limit is exceeded, and a declaration sentence that names every platform that will receive an event. Nothing moves until confirm_lead_move. The preview lasts 30 minutes.
preview_lead_undo
ChatGPTPreview undoing a move batch (the batch_id a confirm returned), within 24 hours of the move. Leads still in the batch's stage go back to their previous stage quietly; leads moved since, or whose previous stage was deleted, stay and are listed by name. When the move sent events, the preview states how many already reached each destination and can't be unsent. Returns a declaration for confirm_lead_undo. An undo can't itself be undone.
query_data
ChatGPTRun a sandboxed ClickHouse SQL query against a store's analytics data. Workspace isolation is automatic. SELECT only, 10s timeout, 10k row limit. Always include a LIMIT clause.
set_custom_store_script
ChatGPTReplace the custom JavaScript on a store using Standard delivery, with the console's rules: at most 100 KB, no <script> tags, and it must compile. Pass source as null to clear it. Omit note to keep the current note. Pass restore_previous true, with no source or note, to put back the version before the last change. Without declaration it returns a preview and the declaration for this change, and changes nothing. With the same arguments and that declaration it applies the change and returns how to undo it.
set_lead_session_settings
ChatGPTChange this session's lead pipeline settings. move_quietly true sends nothing to any destination on every move; false follows each stage's settings. Raising move_cap without consent returns a consent sentence and changes nothing; with that sentence as consent it raises the limit. The limit can't go above 10,000. The result says how to undo the change.
set_route_custom_script
ChatGPTZappush support only. Change one of a route's two add-on script blocks, slot store or gate, with the console's rules: at most 100 KB, no <script> tags, and it must compile. The full replacement scripts can't be changed here. Pass source as null to clear the block. Omit note to keep the current note. Pass restore_previous true, with no source or note, to put back the version before the last change. Without declaration it returns a preview and the declaration for this change, and changes nothing. With the same arguments and that declaration it applies the change and returns how to undo it.
update_compliant_page
ChatGPTChange a compliant page with the same fields as the console's page settings: domain, page_config (text, links, colours), meta_pixel_id, meta_domain_verification and is_active. Custom HTML and files are edited in the console only. Without declaration it returns a preview and the declaration for this change, and changes nothing. With the same arguments and that declaration it applies the change and returns how to undo it.
update_pixel
ChatGPTChange a Meta pixel's label, pixel ID, test event code, whether it sends events (events_enabled) and whether it sends draft orders. The access token is changed only through create_pixel_credential_link. Without declaration it returns a preview and the declaration for this change, and changes nothing. With the same arguments and that declaration it applies the change and returns how to undo it.
update_route
ChatGPTStep 3 of store setup. Change a route's settings with the same fields as the console's route settings: label, compliant page, destination URL, Meta pixel, extra pixels (additional_meta_integration_ids, the full list), destination hosts, link stamping, strategy, status, and is_default. Deactivating a route or making it the default needs an admin. Without declaration it returns a preview and the declaration for this change, and changes nothing. With the same arguments and that declaration it applies the change and returns how to undo it.
verify_compliant_page_domain
ChatGPTCheck a compliant page's DNS records, as the console's Verify button does. Changes no setting, so it needs no preview; safe to call again.