bulk_delete_zones_postback
ChatGPTpostback_url in get_zones first). A zone id that does not exist is refused with 400 "Zones not found: …". Only onclick (TrafficBack) zones are supported.By Propeller Ads Limited
Propush.me is a push and in-page traffic monetization platform for publishers. This plugin connects ChatGPT and Codex to your Propush.me publisher account, so you can work with it in conversation. Check your balance and account access. Pull statistics — impressions, subscriptions and earnings — by day, zone, site, country, OS or sub-ID, including subscriber lifetime value by subscription day. Review your sites and zones with their verification and activity status. Create TrafficBack (onclick) zones on your verified sites, and set, replace or remove postback URLs on TrafficBack zones, one at a time or in bulk. With Landing Constructor access, browse and create landing constructors and read the weekly trending GEOs digest. Search the Propush help documentation for setup answers. You sign in with your Propush.me account through OAuth: the plugin acts only on the account you connect and never sees your password. Limitations: you need a Propush.me publisher account, and the plugin only sees that account's own data. It cannot request payouts or move money, and it cannot delete sites, zones or landing constructors — zones and constructors it creates are permanent. Sub-ID and multi-field statistics reports require the account's extended API access level.
postback_url in get_zones first). A zone id that does not exist is refused with 400 "Zones not found: …". Only onclick (TrafficBack) zones are supported.is_constructor_available from get_me).type 'site' or 'landing' in get_sites — constructor and other placements are refused with 400), owner-verified (user_verification_status 2) and approved by moderation. A site that is not verified, still under moderation or rejected gets a 403 whose hint names the reason, e.g. 'This site has not been verified yet. Please verify site ownership before creating zones.' Moderation status is not part of get_sites, so that hint is the only place it shows up; the site's state has to change before a retry can succeed.postback_url in get_zones first), the zone is not on that site, or the site is not currently approved for new zones (not verified, under moderation or rejected).is_constructor_available from get_me).site_id), human-friendly name, type (landing template, e.g. 'social-survey'), creation timestamp, onclickDomain (the domain its onclick zones are served from, or null when it has none) and its zones — each with id, title, zoneType (the zone's place in the landing, e.g. 'mainExit_currentTab'), direction, isActive, isArchived, postbackUrl ({id, url} or null when none is set) and serviceWorker (the push zone's service worker file as {domain, name, content}; null on other zones). Requires constructor access (see is_constructor_available from get_me). Paginated server-side, ordered by id. The response carries meta { page, page_size, total_items, total_pages, has_more }; page_size defaults to 20 and is capped at 50. To fetch everything, keep page_size fixed and walk page from 1 to total_pages.country_id field of get_statistics rows grouped by country — those rows carry the numeric ID only, so this list is the only way to name them. Filtering does not need this tool: get_statistics takes ISO codes directly.access_level is one of '' (no API access), 'base' (standard access) or 'extended' (adds grouping by request_var and multi-field grouping in get_statistics). is_constructor_available is true when the account may use the Propush landing-constructor tools (get_constructors, get_constructor, create_constructor) and the trending-GEOs digest (get_trending_geos); when false those tools return an access error. is_ai_landing_available is true when the account can create AI-built landings in the Propush dashboard.value (the name get_statistics rows carry in os and its os filter accepts, e.g. 'android') and title (display form, e.g. 'Android'). Requires a Propush account. Filtering does not need this tool: get_statistics takes the names directly — use it to see what names exist.type field: site, landing, constructor, or null in any other case. Only verified (2) sites of type site or landing can take new zones (see create_onclick_zone); moderation approval is required for that too, and it is not reported here. The id here is the site id get_zones reports as site_id, but it is NOT the site_id get_statistics reports or accepts — see get_statistics before filtering a report by site. Paginated server-side, ordered by id. The response carries meta { page, page_size, total_items, total_pages, has_more }; page_size defaults to 100 and is capped at 500. To fetch everything, keep page_size fixed and walk page from 1 to total_pages.os_id arrives with os next to it, the OS name (e.g. 'android') — use the name. It is null when the OS was not detected (os_id 0), and that traffic cannot be filtered at all. The os filter takes names, not IDs; get_os lists them. - country_id is a bare number. get_countries turns it into a country name and ISO code. Filtering does not need that lookup: the countries filter takes ISO codes directly. - affiliate_id identifies a site-and-direction pair. The same number appears as site_direction_id in get_zones. It has no filter of its own, so narrow with zone_ids and directions instead. - zone_id is the id get_zones returns — take the zone's title, and the site it belongs to, from there. - site_id is NOT the id get_sites and get_zones report: statistics numbers sites in a space of its own, so the two never match, and passing a get_sites id as site_ids is refused with "The selected choice is invalid." It has no dictionary of its own — it resolves to a nameable site only through the zones: group by zone_id and read each zone's site_id and title from get_zones (grouping by [site_id, zone_id] gives the pairing directly, but multi-field grouping needs the 'extended' access level). That roll-up is also how to report per site; to narrow to one site you already know, pass that site's zones as zone_ids. site_ids only accepts values that came out of a site_id grouping. tz works only when date_from is within the last 7 days. On an older range the API rejects the whole call with "Time zone is available only in the weekly period." That message is about the date range, not the offset, so a different offset or a retry will not help — either leave tz out (dates are then EST) or move date_from closer to today. Grouping by subscription_date switches to a different report: subscriber lifetime value per subscription day. It has to be the only group_by field and cannot be combined with tz or directions — that report has no room for them, so such a call is refused. date_from/date_to then pick subscription days, not earning days. Each row is one subscription day with subscription_date, subscriptions, money_0-1, money_2-7, money_8-14, money_15-30 and money_30+ (what that day's subscribers earned 0–1, 2–7, 8–14, 15–30 and 30+ days after subscribing; null when nothing), the matching money_percent_* shares of subscriptions_money (the sum of those five), trafficback_money, and total_money (subscriptions_money plus trafficback_money). None of the regular metrics are there — no impressions, no money. zone_ids, site_ids, countries, os and request_vars narrow it as usual. Examples: - Daily earnings: { date_from: "2024-01-01", date_to: "2024-01-07", group_by: ["date_time"] } - By country: { ..., group_by: ["country_id"] } - Specific zones: { ..., group_by: ["zone_id"], zone_ids: [123, 456] } The response is { result: [ ...rows ], meta: { total_items, total_pages, page_size, page } }. page_size is capped at 200 rows so that one page fits the client's result-size limit — check meta for the window that was actually applied. For a report that spans pages, keep page_size as it is and walk page from 1 to meta.total_pages, though narrowing the dates, the filters or group_by usually beats paging through everything.metadata (slug, publishedAt) and a data payload. The data structure is digest-specific and is not covered by backward-compatibility guarantees — it may change without notice, so read the values as they come rather than relying on a fixed shape. Until a digest has been published the call fails with "No trending GEOs digest has been published yet." — digests are published periodically, so an immediate retry returns the same. Requires constructor access (see is_constructor_available from get_me).zone_id), title, site_id (the same id get_sites returns, and not the site_id get_statistics reports), direction_id (72=Push Notifications, 73=Traffic Back), active status, site_direction_id (the number get_statistics reports as affiliate_id) and postback_url ({url}, or null when no postback is set — the ground truth for the postback tools). Paginated server-side, ordered by id. The response carries meta { page, page_size, total_items, total_pages, has_more }; page_size defaults to 100 and is capped at 500. To fetch everything, keep page_size fixed and walk page from 1 to total_pages. Prefer the site_id filter over walking many pages when you only need one site's zones.search_docs.hits[].uri). Landing Constructor entries require constructor access (see get_me); without it the call returns an access error.read_doc tool with a URI to fetch full Markdown. Landing Constructor docs are searched only for accounts with constructor access (see is_constructor_available from get_me); other accounts get Help Center hits only.Click any prompt to copy it.
Add this badge to your site or README. It links to this page.
HTML
<a href="https://mcp-app-store.keenethics-labs.com/app/propush-me"><img src="https://mcp-app-store.keenethics-labs.com/badges/listed-on-mcp-app-store.svg" alt="Listed on MCP App Store" width="220" height="44"></a>
Markdown
[](https://mcp-app-store.keenethics-labs.com/app/propush-me)