Edit per license event filter details#3921
Conversation
✅ Deploy Preview for replicated-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for replicated-docs-upgrade ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
replicated-ci
added
type::docs
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
| <li>First Access for Selected License Type: Triggers a notification the first time that a customer with a specific license type accesses the Enterprise Portal. For example, if you select "Paid" for the License Type filter, then you will receive a notification the first time that a customer with a Paid license access the Enterprise Portal, even if they previously logged in when they had a Trial license.</li> | ||
| </ul> | ||
| <p>First Access for Selected License Type only tracks Enterprise Portal access events that occur after March 27, 2026.</p> | ||
| </td> |
There was a problem hiding this comment.
First Access for Selected License Type only tracks Enterprise Portal access events that occur after March 27, 2026.
Is this true for Enterprise Portal Access Granted per-license type events as well?
The original note for the Assets Downloaded event type (https://github.com/replicatedhq/replicated-docs/pull/3916/changes#diff-29ef7f7ee6ea45aa9c4b78b07e0a25acf8845674d0aed4d9e509c13d5f839629R198) used the phrase "per-license-type milestones", and I wasn't sure if that broad term was intended to cover the per license type filters for both Assets Downloaded and Enterprise Portal Access Granted events
There was a problem hiding this comment.
Yes to both. PR vandoor#9313 (merged March 27, 2026) introduced per-license-type milestone tracking for both events in the same change. It created two new tables:
software_pull_milestones (for Release Assets Downloaded)
enterprise_portal_access_milestones (for EP Access Granted)
Both tables are forward-only (INSERT IGNORE, write-once). The original "per-license-type milestones" phrasing was intentionally broad because it covered both. So the note "First Access for Selected License Type only tracks Enterprise Portal access events that occur after March 27, 2026" is correct. The March 27 date is the merge/deploy date of #9313, and the same cutoff applies to both event types.
| <li>First Pull Only: Triggers a notification only the first time that a customer pulls a release asset.</li> | ||
| <li>First Pull for Selected License Type: Triggers a notification the first time that a customer pulls a release asset with the selected license type. For example, if you select "Paid" for the License Type filter, you will receive a notification the first time that a customer pulls a release asset using a Paid license, even if the customer had previously pulled assets using a Trial license.</li> | ||
| </ul> | ||
| <p>For customers who pulled software before March 18, 2026, the Vendor Portal applies <code>is_first_customer_pull: false</code> on all subsequent pulls. **First Pull for Selected License Type** only tracks asset pulls that occur after March 27, 2026.</p> |
There was a problem hiding this comment.
First Pull for Selected License Type only tracks asset pulls that occur after March 27, 2026.
Want to confirm that this re-word is still accurate. I wasn't 100% certain about what was included in the original "per-license-type milestones" phrasing
There was a problem hiding this comment.
Yes, that's accurate. The per-license-type pull tracking was part of the same March 27 PR (#9313). Note this is a different cutoff than the original is_first_customer_pull tracking, which was introduced on March 18 via PR #9206. So the existing docs are correct that there are two dates:
March 18: is_first_customer_pull (the global "First Pull Only" filter) started tracking
March 27: per-license-type milestones (both "First Pull for Selected License Type" and "First Access for Selected License Type") started tracking
|
|
||
| :::note | ||
| Use "First Pull for Selected License Type" rather than "First Pull Only" if customers may start on a trial before converting to a paid license. "First Pull Only" tracks the first-ever pull regardless of license type. If a customer pulls on a trial license first, the notification will not fire again after they convert to paid. "First Pull for Selected License Type" tracks milestones per license type. The notification fires the first time the customer pulls software with a paid license, even if they previously pulled on a trial. | ||
| ::: |
There was a problem hiding this comment.
^ figured this was already covered well in the reference doc for event types and filters
3 participants
Edits https://github.com/replicatedhq/replicated-docs/pull/3916/changes