ReleasePad can track which users view your changelog posts. This lets you see reader-level analytics — who opened what, and when — right inside your dashboard.

How it works

Your widget code includes a data-user-metadata attribute. When you populate it with the current user’s email or ID, ReleasePad associates each page view with that user.

Step 1: Find the data tag

Open your widget code (from General Settings → Code) and locate the data-user-metadata attribute on the rp-token div:

<div id="rp-token"
     data-param="YOUR_TOKEN"
     data-user-metadata=""
     lang="en">
</div>

Step 2: Populate it with the current user

Use your server-side language to fill data-user-metadata with the logged-in user’s email or ID every time the page loads.

Ruby on Rails example:

<div id="rp-token"
     data-param="YOUR_TOKEN"
     data-user-metadata="<%= @user.email %>"
     lang="en">
</div>

PHP example:

<div id="rp-token"
     data-param="YOUR_TOKEN"
     data-user-metadata="<?php echo $user->email; ?>"
     lang="en">
</div>

JavaScript (dynamic):

<div id="rp-token"
     data-param="YOUR_TOKEN"
     data-user-metadata=""
     lang="en">
</div>

<script>
  // After your auth logic resolves:
  document.getElementById('rp-token')
    .setAttribute('data-user-metadata', currentUser.email);
</script>

Step 3: Deploy

Copy the updated code into your application and deploy. Once live, ReleasePad will start recording which users view each post in your analytics dashboard.

Important: The data-user-metadata value must be set on every page load. If the attribute is empty, the view is recorded as anonymous.

Need more help?

Can't find what you're looking for? Our team is happy to help you get set up.

Contact support