Documentation

Everything you need to send your first push and grow your audience.

Getting started

1. Create your free account at natom.app/app.
2. From the Sites section, add your site with a name and its domain.
3. Install the code as described below: from that moment your visitors can subscribe to notifications.

Installing on your site

You need two things, both available from the Code button on your site's row:

1. The snippet in your pages

<script src="https://cdn.natom.app/push.js?k=YOUR-KEY" async></script>

Add it to every page, ideally before the closing </body> tag. On WordPress you can use your theme (footer.php) or any script-injection plugin.

2. The service worker in your root

Download natom-sw.js from the dashboard and upload it to the root of your domain, so it responds at https://yoursite.com/natom-sw.js. It is the component that receives and displays notifications even when your site is closed.

Opt-in prompt

From the editor you also pick the size (small, medium, large) and the position, separately for desktop and mobile: top, center or bottom. The categories panel uses the same size and has its own position. The preview updates as you edit.

The browser's notification permission deserves to be asked well: Natom first shows your own customizable prompt, and only after a click the system request. From the Popup button you configure copy, icon, colors, position, display delay and how many days to wait before asking again, with a live desktop and mobile preview. Changes reach visitors within 5 minutes.

Prefer to hook subscription to your own button? Call natom.ask() from JavaScript and disable the automatic prompt.

Campaigns

From New push you compose the notification: title, body, destination URL, optional icon and image.

• Immediate or scheduled: set a date and time and Natom takes care of it.
• Cross-domain: select multiple sites and the same push goes out to all of them in one shot, with aggregated stats.
• TTL: if a notification isn't delivered within the set hours (browser off), it expires instead of arriving late.

At the top of the Campaigns page pick a period (today, yesterday, 7, 30, 90 days, 12 months or a custom range): the tiles show sent, delivered, clicks and CTR for the period, the chart the trend, and the table the campaigns of those days. Deliveries and clicks are attributed to the send day; over long periods the chart groups by week or month, so even years of history stay light.

Audiences

An audience is a group of subscribers defined by tags. Your site assigns tags with one line of JavaScript:

natom.tag('cat_sports', '1')     // on sports pages
natom.tag('cat_politics', '1')   // on politics pages

On a CMS the value is dynamic: a single line in your article template profiles every reader automatically. Tip: use one tag per category (as above), so interests accumulate and a reader can belong to multiple audiences.

From your site's Audience button you create the segment (e.g. "Sports readers" = cat_sports = 1): existing matches are included instantly, new ones join on their own. In New push, with a single site selected, pick the target audience from the menu.

Let readers choose (explicit preferences)

If you would rather have readers say what they want, enable Let readers pick categories in the prompt editor and list the categories. Right after opting in, a panel with checkboxes appears: readers tick what they care about and can change it any time from a link <a href="#" data-natom-prefs>Manage notifications</a> you place anywhere (footer, a dedicated page). Every category is an audience: audience sends and RSS routing work exactly the same. Readers who pick nothing receive everything you send to "all subscribers". The choice belongs to the reader: no automatic mechanism adds them to categories they did not tick.

Geo-targeted sends

Every subscriber automatically gets the system tag geo with their country (e.g. geo = IT), detected from the browser time zone: an "Italy" audience is just the filter geo = IT and the push goes out there only. For finer targeting (ZIP code, city, region) use tagging where your site actually knows the data because the user provided it: natom.tag('zip','57128'), then build the audience on that tag. It is the most accurate method there is: the data comes from the user, not from an IP guess.

Automatic RSS

From the RSS button you connect one or more feeds (RSS 2.0 or Atom). For every new article Natom builds the push with title, excerpt and image:

• Automatic sending or a draft to approve, your choice.
• Audience routing: when enabled, each article is sent to the audience matching its category. Matching uses the cat_<category> convention (lowercase, spaces become _): an article in "Sports" looks for the audience filtering on cat_sports. If none matches, the push goes to everyone.

Analytics

• Active subscribers and day-by-day growth, plus breakdowns by country, device, browser and OS. The chart counts active subscribers only: a token deactivated by cleanup disappears from history too, so the cumulative line always matches the number at the top.
• Delivered: notifications actually displayed on the reader's screen. Up to 5,000 active subscribers per site the count is exact; above that it is a 20% sampled estimate (the service worker reports one notification in five and Natom scales up), which is accurate at large volumes and keeps analytics light.
• Clicks and CTR per campaign, tracked at 100%.
• Prompt: how many times it was shown, accepted or postponed, day by day.

Plans and limits

Pushes are always unlimited, on every plan. When you exceed your plan's subscriber cap you have 5 days to upgrade: everything keeps working normally in that window. After the 5 days, new subscriptions are paused (your existing audience keeps receiving pushes, you lose nothing). The yearly plan costs 10 monthly payments: 2 months free.

Migrating to Natom from another provider

If you currently use another web push platform, you can switch to Natom without losing the ability to reach your audience. One thing must be said clearly first, because it applies to any provider change:

GDPR and privacy

Web push sent through Natom is GDPR compliant by the very way the mechanism works:

• Explicit prior consent: no notification can be sent unless the user accepted the browser permission request, an active and granular opt-in (art. 6.1.a GDPR).
• No personal data required: subscribing asks for no email, name or other direct identifiers. Natom processes a pseudonymous technical token generated by the browser, the browser and OS type, and any tags assigned by your site.
• Self-service revocation: users can turn notifications off at any time from their browser settings, with no middleman. Revoked tokens become unusable and are removed by periodic cleanups.
• Data minimization: statistics are aggregated; impressions are sampled, never tracked per user.
• Clear roles: for your sites' subscriber data you are the data controller and Natom acts as processor under art. 28 GDPR.

Questions? Write to support@natom.app.