đź“–
PixieBrix Documentation
đź“Ł

Campaign Management

ℹ️
Campaigns are currently in preview. Contact hello@pixiebrix.com to enable campaigns on your account

Campaigns

A Campaign is a reporting entity to track engagement of a set of team members. Unlike Groups, Campaigns do not impact team member permissions.

To access your Organization’s Campaigns, click the Campaigns button on the My Team page:

image

Creating/Updating Campaigns

Creating a Campaign

To create a Campaign, click the Create Campaign button.

Provide a unique Campaign name, and click to upload CSV file containing the list of members in the campaign. The upload CSV file must have the following columns:

  • Email: the members email address

You can optionally provide additional custom columns for reporting. For example:

  • Office: the site/location of the team member
  • Organization Unit: the business unit of the team member

image

Updating a Campaign

⚠️
The uploaded list of members replaces the current members of the campaign

To update the members associated with the campaign, click the “Edit Campaign” button on the Campaign Detail page:

image

The upload CSV format has the same structure for campaign creations.

In order to facilitate re-upload of a member list generated via “Export” (see Campaign Details below), the following columns in the upload file are ignored:

  • Status
  • Date Joined
  • Extension Version
  • Last Seen

Campaign Reporting

Campaign Summary

Associated Groups Card

The Associated Groups Card shows Groups that campaign members are in, and the number of campaign members in each group.

Associated Deployments Card

The Associated Deployments Card shows deployments assigned to members of the campaign via the Associated Groups (see above)

Campaign Details

The Campaign Details table shows a list of all members in the Campaign, their status, and the additional data uploaded for reporting.

Export

To Export the table of campaign members as a CSV, click the Export button:

image

Status

The Status column shows the team member’s engagement status:

  • In Campaign
  • Assigned Group
  • Assigned Deployment
  • Registered with PixieBrix
  • Linked Chrome
  • Recent Heartbeat
  • Installed Deployments
  • Engaged

Date Joined

The Date Joined column is the date that the member first registered with PixieBrix

PixieBrix Version/Last Heartbeat

When an enterprise team member has the PixieBrix Browser Extension installed, the extension pings the server every 5 minutes to determine if new Deployments are available. During this check, the extension also reports metadata about the install

The PixieBrix Version is the version of the PixieBrix Browser Extension

The Last Heartbeat timestamp is the time (in UTC) that PixieBrix last received a ping from the team member’s browser extension.

Groups

The Groups columns lists the Groups of which the campaign member is a member of

❓ Troubleshooting

The campaign member is linked, but has not sent PixieBrix a heartbeat in the last week

If the campaign member is linked/registered, but has not sent a heartbeat to PixieBrix in the last week, one of the following might be occurring:

  • The member is on vacation/out of office for over a week
  • The member is not using the computer/browser/browser profile that has the linked PixieBrix Extension installed. For example:
    • The member is using the “Guest” profile on Chrome
    • The member is using Microsoft Edge instead of Chrome
  • The member linked a different account, for example, a personal account
  • Your network or VPN is blocking POST requests to https://app.pixiebrix.com/api/deployments/
  • The member has disabled the PixieBrix Extension in Chrome. Check if the Group Policy Object your IT team used to force install the PixieBrix Extension permits disabling the extension
  • The member cleared the access token from extension storage
    • Unrestricted members can unlink the extension on the Settings screen of the Extension Options page. The button is hidden for restricted enterprise members
    • The member has cleared the local data for their browser extensions (by installing a browser extension with that capability, or manually using the file system). PixieBrix uses Chrome’s storage.local API for storing the member’s access token in the browser
  • The member is on a PixieBrix version prior to 1.5.2 (Released January 30, 2022) and does not have any deployments installed. Prior to 1.5.2, the PixieBrix Extension sent a heartbeat when linking the extension, and then only if the user had any deployments installed

Twitter