Campaigns

A campaign is one push notification, or a series of them, sent to the subscribers of a site. This page walks through creating one in the dashboard. To do the same from your own code, see the REST API Reference.

To start, open Campaigns → Create Campaign in the sidebar.

#Standard or Live

The first choice is how often the campaign sends.

	Standard	Live
Sends	Once	Up to 5 times, the first send included
Best for	Promotions, new articles, announcements	Stories that keep developing: a match, an election, breaking news
On the device	Each campaign is its own notification	Each update replaces the previous one instead of piling up
Ends	After it sends	When you complete it, or after the 5th send

#The notification

Field	What it's for
Campaign name	A private label so your team can find the campaign later. Subscribers never see it.
Title	The bold headline. Max 65 characters.
Message	The text under the title. Max 160 characters.
Destination URL	The page people land on when they tap the notification.
Icon	A small square image next to the title, usually your logo. A 192×192 px PNG works best. Your 5 most recent icons are offered for quick reuse.
Image	An optional large banner shown when the notification is expanded. It's most reliable on Chrome and Android, and some browsers don't show it at all.

The preview next to the form shows roughly how the notification will look on each system. The real look depends on the subscriber's browser and OS.

#Link tracking

Turn on Link tracking to add UTM tags to the destination URL, so tools like Google Analytics can count the visits that came from the notification:

 1https://example.com/offers?utm_source=sharepush&utm_medium=push&utm_campaign=new-drop-is-live

utm_campaign is built from the title. The final link is shown under the field before you send.

#Bounce URL

By default a click takes the subscriber straight to the destination URL. With Bounce URL turned on, the click first opens a page you choose, with the destination added as ?dest=.... The SharePush SDK on that page records the visit, then forwards the visitor to the destination.

Use it when the destination is on a site that doesn't run the SharePush SDK, such as a partner's site or a store on another domain. Without it, those clicks still count, but Viewed can't be measured, because nothing on the destination page can report the visit. See Viewed.

The bounce page must be on your own site and must load the SharePush SDK, otherwise the visitor won't be forwarded. Enter it as a full URL, such as https://example.com/go. The API also accepts a path.

#Choosing the audience

By default a campaign goes to every active subscriber of the site. To narrow it down, tick one or more:

Browsers, such as Chrome, Safari or Firefox.
Operating systems, such as Android, iOS or Windows.

The lists only show browsers and systems your subscribers actually use. Estimated reach updates as you tick boxes, showing how many active subscribers match. Inside a group, any ticked value matches (Chrome or Safari). Across groups, all must match (Chrome and Android).

The API can also filter by country.

#Sending

Pick an option next to Launch Campaign:

Option	What happens
Send Now	Sending starts right away. You land on the campaign page, where the numbers start coming in.
Schedule	Pick a future date and time. The campaign waits in the Queue and sends automatically.
Draft	Saves the campaign without sending. Open it later from Campaigns List and send it from its page.

Drafts and filters: audience filters apply only to Send Now and Schedule. A draft sent later from its campaign page goes to all active subscribers of the site.

#Live campaigns: sending updates

After a live campaign's first send, open it from Campaigns List to post updates. Each update has its own title, message and optional image, and can be sent now, scheduled or saved as a draft. You can edit a draft update and send it whenever you're ready.

Renotify: by default a new update quietly replaces the previous notification. Tick Enable Renotify to make the device alert again (sound or vibration) for that update. Use it for the moments that matter, not every update.
The limit: a live campaign holds 5 sends, the first one included, so you get 4 updates after creating it. Once it's full, start a new live campaign.
Completing: when the story is over, mark the campaign as completed from its page. A completed campaign can't send again.

#The Queue

Campaigns → Queue shows what's coming up and what's in progress:

Live campaigns that are running and can still receive updates.
Campaigns that are scheduled or sending right now.
Live updates that are scheduled or on their way.

Use Inspect on any row to open the campaign.

#After sending

The campaign page shows how the notification performed: how many were delivered, clicked and dismissed, and when. To understand each number and why they differ, see the Metrics Glossary.