AimTell
AimTell is a web push notification platform for managing websites, subscribers, campaigns, segments, and delivery analytics.
Verdict
Common use cases
- Draft campaign copy for next product launch
- Pull last month's click rates for exec report
- Build segment for cart abandoners over $100
- Compare conversion metrics across three campaigns
- Review sampled delivery logs for troubleshooting
Integration
- Vendor
- AimTell
- Category
- other
- Auth
- API_KEY
- Tools
- 15
- Composio slug
aimtell
Tools
- Create Manual Campaign
Create a manual push campaign as a draft only; this tool never schedules or sends it.
- Create Segment
Create a named audience segment for a website from an AimTell segment definition.
- Delete Manual Campaigndestructive
Permanently delete one manual campaign by ID. This destructive action cannot be undone and permanently removes the campaign.
- Delete Segmentdestructive
Permanently delete one audience segment by ID. This destructive action cannot be undone; it removes the segment but does not delete its subscribers.
- Get Analytics Over Time
Return a daily AimTell metric over a date range for all websites or one website.
- Get Campaign Results
Return daily send, delivery, bounce, click, conversion, and available revenue results for a manual, event-triggered, RSS, or welcome campaign.
- List Campaigns
Return one page of manual, event-triggered, RSS, or API push campaigns for an AimTell website.
- List Notification Logs
Return one page from AimTell's sampled notification log for the last seven days, optionally filtered to one subscriber. This is not a complete delivery ledger and does not include every notification sent to every subscriber.
- List Segments
Return all audience segments for an AimTell website, including the IDs and definitions used for subscriber filtering and campaign targeting.
- List Subscribers
Return one page of subscribers for an AimTell website, optionally filtered by segment or subscriber ID and optionally including attributes or notification history. AimTell may return processing=true with no subscriber page while it prepares
- List Websites
Return one page of websites available to the connected AimTell account, including site IDs needed by other tools. Use next_cursor to retrieve later pages.
- Send Push Notification
Immediately send a one-off push notification to exactly one explicitly selected audience: subscriber IDs, one segment, one alias, or the website's full reachable audience. Delivery begins immediately, cannot be undone, and has no dry-run mo
- Set Subscriber Attributes
Set custom attributes on one subscriber identified by subscriber UID, user alias, or email alias; supplied aliases may also be associated with the subscriber.
- Update Manual Campaign
Update the content or targeting of an unscheduled, unsent, non-A/B manual campaign draft without scheduling or sending it.
- Update Segment
Change the name or audience definition of an existing AimTell segment.
Setup
Setup guide
- 11. In Switchy, open your workspace settings and navigate to the Integrations tab. 2. Click 'Add MCP Integration' and select AimTell from the catalog. 3. You'll be prompted to paste an AimTell API key — generate one by logging into your AimTell account, opening Settings > API Access, and copying the key labeled 'Read/Write'. 4. Paste the key into Switchy and click 'Connect'. 5. Switchy will verify the key and list the websites in your AimTell account. 6. To test, open any Project and type '@AimTell list my campaigns for [your website domain]' — you should see a table of recent campaigns. 7. If the connection fails, double-check the key has both read and write permissions enabled in AimTell.
What teammates see: by default, memories from AimTell are scoped to the Project (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Projects have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
Draft Launch Campaign
@AimTell create a manual campaign draft for our main website with the title 'New Dashboard Live', message 'Explore faster reporting and custom views', and link to https://example.com/dashboard-update
Weekly Performance Summary
@AimTell show me campaign results for all campaigns on our site from the last seven days, including sends, clicks, and conversions
Build High-Value Segment
@AimTell create a segment called 'Pricing Visitors - No Purchase' for our main site, filtering subscribers who viewed /pricing in the last 30 days and have zero orders
Compare Campaign CTR
@AimTell get campaign results for campaign IDs 12345 and 12346, and show me the click-through rate for each
Audit Recent Deliveries
@AimTell list notification logs for the last seven days on our site, filtered to subscriber ID sub_abc123
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@AimTell show me the click-through and conversion metrics for our Black Friday campaign from last week
The Black Friday campaign (ID: camp_bf2024) sent 47,320 notifications between Nov 29–Dec 1. Daily breakdown: 18,450 clicks (39% CTR), 2,103 conversions (4.4% conversion rate), $31,547 attributed revenue. Peak engagement occurred Nov 29 at 2pm EST with 8,200 clicks in one hour. Bounce rate held steady at 2.1% across all three days. This illustrative summary reflects the structure AimTell returns; actual figures depend on your campaign configuration and subscriber engagement.
This example highlights AimTell's campaign analytics tool, which aggregates performance data across send/delivery/click/conversion dimensions. Requires API key with read access to campaign results. Note that revenue attribution depends on conversion tracking being configured in your AimTell account before the campaign ran.
@AimTell create a draft campaign titled 'Holiday Sale Reminder' targeting our high-value segment with the message 'Last chance: 30% off ends tonight'
Draft campaign created successfully (ID: camp_hs_draft_9472). Title: 'Holiday Sale Reminder'. Target segment: high-value (12,840 subscribers). Message: 'Last chance: 30% off ends tonight'. Status: DRAFT—not scheduled or sent. You'll need to log into the AimTell dashboard to set delivery timing, add a destination URL, configure action buttons, and manually publish. This tool creates the campaign shell but intentionally stops short of scheduling to prevent accidental sends.
Demonstrates AimTell's manual campaign creation tool, which always produces a draft. This is a safety feature—the MCP cannot schedule or send notifications, only prepare them for human review. You must complete setup (URL, timing, buttons) in the AimTell UI before the campaign goes live, preventing unintended blasts.
@AimTell pull the last 50 notification logs for subscriber sub_ak8j3m and summarize any delivery failures or bounces
Retrieved 50 sampled notification events for subscriber sub_ak8j3m (Dec 10–16). 47 delivered successfully, 3 bounced due to 'subscriber unsubscribed' on Dec 12. No other delivery failures detected. Logs show engagement with 'Winter Sale' campaign (clicked Dec 11, 9:14am) and 'New Arrivals' campaign (delivered but not clicked, Dec 14). Important: AimTell's log API samples the last 7 days only and does not guarantee complete delivery history—use this for spot-checking, not compliance auditing.
This synthesis example pairs AimTell's notification log tool with AI reasoning to surface patterns. The log API is sampled and limited to 7 days, so it's best for troubleshooting recent issues, not forensic analysis. Requires API key with log read access. The AI can identify bounce reasons but cannot recover older records or guarantee completeness.
Use-case deep-dives
When AimTell beats email for abandoned-cart nudges
A 6-person Shopify store team sends 200 cart-recovery messages daily to subscribers who bail at checkout. Email open rates hover at 18%; browser push through AimTell hits 40% within the first hour because the notification lands on the subscriber's device whether they're checking email or not. The team uses Create Manual Campaign to draft a recovery message, Get Campaign Results to track conversions, and List Notification Logs to debug delivery issues for high-value carts. The trade-off: AimTell requires the subscriber to opt in via browser prompt, so your addressable audience is smaller than your email list—typically 8-15% of site visitors. If your cart value justifies the setup and your audience skews mobile-first, the click-through lift pays for itself in two weeks.
Targeting power users without spamming the full list
A 12-person product team at a project-management SaaS needs to announce a new Gantt view to the 400 users who requested it, without notifying the other 8,000 subscribers. They use Create Segment to build an audience from AimTell's subscriber metadata (tags like 'requested_gantt' or usage frequency), then draft a manual campaign that only reaches that cohort. Get Analytics Over Time confirms the segment's engagement baseline before the send. The limitation: AimTell's segmentation relies on data you've already pushed to their API or captured via on-site behavior; if your user attributes live in Postgres and you haven't synced them, you're building segments blind. For teams that instrument their site events and keep AimTell's subscriber records current, this beats a Mailchimp blast because the notification arrives in-app, not buried in an inbox.
Real-time push when a story breaks at 2am
A 4-person newsroom publishes 12 stories daily; three times a month, something breaks outside business hours and the team needs to drive immediate traffic. They use Create Manual Campaign from a Slack workflow to draft a push notification, review the headline in AimTell's dashboard, and send it to their 15,000 subscribers within five minutes. List Campaigns lets the editor confirm the send went out; Get Campaign Results shows click-through by the hour so they know whether to follow up with a second push. The constraint: AimTell's notification log only samples the last seven days, so if you need a full delivery audit trail for compliance or attribution, you're exporting daily or accepting gaps. For publishers where speed trumps forensic logging and the revenue per click justifies the API-key setup, this turns a manual process into a two-click deploy.
Frequently asked
What does the AimTell MCP let me do in Switchy?
It lets your AI assistant create and manage web push notification campaigns in AimTell. You can draft campaigns, build audience segments, pull analytics, and review delivery logs without leaving the conversation. The MCP never auto-sends campaigns—it only creates drafts, so you stay in control of what goes live.
Do I need an AimTell API key to connect this?
Yes. The MCP uses API key authentication, so you'll need to generate one from your AimTell account settings. Any team member with API access can connect it—you don't need admin rights to the AimTell account itself, just a valid key with the permissions you want to expose.
Can the MCP send push notifications immediately?
No. It only creates campaigns as drafts. You still log into AimTell to review, schedule, or send them. This design prevents accidental sends and keeps a human in the loop for anything customer-facing. If you need instant sends, use AimTell's API campaigns tool directly.
How is this different from using AimTell's dashboard?
The MCP is faster for repetitive tasks—building segments from natural language, pulling campaign results across date ranges, or checking logs for a specific subscriber. The dashboard is still better for visual campaign design and A/B testing. Use the MCP when you want data or drafts; use the dashboard when you want control.
Does connecting AimTell count against my Switchy plan limits?
No. MCP connections don't count as seats or integrations in Switchy. The only limit is your AimTell account's own API rate limits—typically generous for normal use. If you hit them, you'll see rate-limit errors in the chat, not in your Switchy billing.