# Which personalization platforms do teams keep using beyond rollout instead of quietly reverting to what they had?

<p class="elv-tracking-normal elv-text-default elv-font-figtree elv-text-base elv-leading-base elv-font-normal" elv="true">Hi G2 reviewers, which<a class="a a--md" elv="true" href="https://www.g2.com/categories/personalization"> </a><a class="a a--md" elv="true" href="https://www.g2.com/categories/personalization">personalization</a> platforms do teams keep using beyond rollout rather than quietly reverting? What seems to decide it:</p><ul>
<li>Whether the reporting shows a clear before and after, or just activity</li>
<li>Whether attribution can be traced back to a source rather than assumed</li>
<li>Whether the data model holds up once someone leaves</li>
<li>Whether the next change is easier than the last one</li>
<li>
<a class="a a--md" elv="true" href="https://www.g2.com/products/ortto/reviews"><strong>Ortto</strong></a> keeps customer data, automation and analytics in one place, with session data such as UTMs used to establish where a user came from. Reviewers say it can get technical, and certain settings are hard to locate.</li>
<li>
<a class="a a--md" elv="true" href="https://www.g2.com/products/customer-io/reviews"><strong>Customer.io</strong></a> triggers off product events, so what fires and why is traceable in the payload. Reviewers advise settling the attribute schema early, since near-duplicate attributes get awkward to clean up later.</li>
<li>
<a class="a a--md" elv="true" href="https://www.g2.com/products/wingify-vwo-testing/reviews"><strong>VWO Testing</strong></a> keeps a record of experiments and results rather than one-off changes, which is what gives a team something to point at a year in. Reviewers say deeper analytics take time to interpret and reports could be more customisable.</li>
</ul><p class="elv-tracking-normal elv-text-default elv-font-figtree elv-text-base elv-leading-base elv-font-normal" elv="true">Plenty of these get bought, configured and then slowly abandoned. Usually not because they broke, but because nobody could show what they were contributing. What kept yours alive past the first six months, the results or the person who owned it?</p><p class="elv-tracking-normal elv-text-default elv-font-figtree elv-text-base elv-leading-base elv-font-normal" elv="true"></p><p class="elv-tracking-normal elv-text-default elv-font-figtree elv-text-base elv-leading-base elv-font-normal" elv="true"></p>

##### Post Metadata
- Posted at: 3 days ago
- Author title: Tech Consultant
- Net upvotes: 1


## Comments
### Comment 1

&lt;p&gt;I think the results keep the platform alive, but ownership is what keeps those results visible. VWO Testing keeping a record of experiments and outcomes feels useful here because the team has something concrete to revisit when someone asks what the platform has actually contributed.&lt;/p&gt;

##### Comment Metadata
- Posted at: 3 days ago





## Related discussions
- [How well does Trello scale into a larger team?](https://www.g2.com/discussions/1-how-well-does-trello-scale-into-a-larger-team)
  - Posted at: over 13 years ago
  - Comments: 6
- [Can we please add a new section](https://www.g2.com/discussions/2-can-we-please-add-a-new-section)
  - Posted at: over 13 years ago
  - Comments: 0
- [Quantifiable benefits from implementing your CRM](https://www.g2.com/discussions/quantifiable-benefits-from-implementing-your-crm)
  - Posted at: over 13 years ago
  - Comments: 4