Aimtell

Overview

Aimtell is a web push notification platform that enables websites to re-engage visitors through browser-based push messages. Unlike email or SMS marketing channels, Aimtell operates through the browser's native Push API and service worker infrastructure, meaning notifications reach subscribers even when the originating website is not open. The platform supports audience segmentation, drip campaigns, and triggered notifications based on visitor behavior.

What This Script Does

When loaded, Aimtell's JavaScript SDK (typically served from cdn.aimtell.com) performs several operations:

• Prompts visitors with a browser-native or custom notification permission dialog requesting push notification access
• On permission grant, registers a service worker (commonly aimtell-worker.js) scoped to the site's origin
• Generates a unique subscriber identifier and transmits it to Aimtell's servers along with browser type, OS, and device metadata
• Stores subscriber state in cookies or localStorage to suppress repeat permission prompts and link the browser to the Aimtell subscriber profile
• Receives and renders push notification payloads via the service worker, including title, body, icon, and click-through URL
• Tracks notification delivery, display, and click events, sending engagement data back to api.aimtell.com

Network requests are made to Aimtell's API endpoints during subscription registration and engagement event reporting. The service worker persists beyond the page session, enabling notification delivery at any time.

Consent & Compliance

Aimtell's scripts serve a marketing function: they build subscriber lists and deliver promotional or re-engagement messages to segmented audiences. Under GDPR and the ePrivacy Directive, push notification subscription constitutes both storage of information on the user's device (service worker registration) and processing of personal data (subscriber identifiers, engagement tracking). Prior consent is required before loading the SDK or prompting for notification permissions.

Under CCPA, the subscriber identifiers and behavioral engagement data collected qualify as personal information. Aimtell should be disclosed in the privacy policy, and the data sale/sharing implications of transmitting subscriber data to a third-party platform must be addressed.

The consent category for Aimtell is marketing.

Should You Block This Without Consent?

Yes.

Aimtell's sole purpose is building push notification subscriber lists and delivering marketing campaigns. The SDK registers service workers, creates persistent subscriber identifiers, and tracks notification engagement — all activities that require prior consent under GDPR and ePrivacy rules. No part of Aimtell's functionality is necessary for core website operation.