Profile Events - Time to Live
Profile Events in Apsis One have a default time to live (TTL). The Event data is stored for a certain time period before it is automatically deleted. Attributes and Tags do not have limited life time.
Profile Events TTL are presented in tables below (applies to account created after January 13th 2025). In case you wish to adjust your Event data lifetime, please reach out to our Customer service.
📝 Note on Custom Events Custom Events that you create yourself do not have a default TTL — you set TTL when creating the Event.
How TTL works
Each Event in Apsis One has a default lifetime measured in years. When an Event is logged on a Profile, it is stored for that fixed period and then automatically deleted. The Profile itself is not deleted — only the Event record.
A few details worth knowing:
Each Tool owns the default TTL for the Events it creates. The Email Tool sets the TTL for email Events, the SMS Tool for SMS Events, and so on.
For Custom Events, you set the TTL when you create the Event. There is no system default.
Events related to consent have a much longer TTL (typically 80 years) because they must be retained for legal traceability.
Events related to bounces are also retained for 80 years so that deliverability suppression decisions remain auditable.
The tables below list all current default Event TTLs, grouped by Tool.
Profile Event TTL
Audience
Profile Event | ID | Time to live |
Profile merge | com.apsis1.events.profile.merge | - |
Profile unmerge | com.apsis1.events.profile.unmerge | - |
Profile key removed | com.apsis1.events.profile.key-removed | - |
Profile delete | com.apsis1.events.profile.delete | - |
Pro Account sync | com.apsis1.events.email.pro.consent | 3 |
Event Updated | {attribute-discriminator}.update.{uuid} | Earlier value stored for 80 years if Event contains consent data. |
Event Created (date) | {attribute-discriminator}.create.{uuid} | 80 years if Event contains consent data. |
Email tool
Profile Event
| ID | Time to live |
Email bounce | com.apsis1.events.email.bounce | 80 |
Email sent | com.apsis1.events.email.sent | 3 |
Email delivered | com.apsis1.events.email.delivered | 3 |
Email open | com.apsis1.events.email.open | 3 |
Email click | com.apsis1.events.email.click | 3 |
Email unsubscribe | com.apsis1.events.email.unsubscribe | 3 |
Email abuse | com.apsis1.events.email.abuse | 3 |
Email A/B test | 'com.apsis1.events.email.split-test | - |
Transactional email bounce | com.apsis1.events.transactional-email.bounce | 80 |
Transactional email sent | com.apsis1.events.transactional-email.sent | 3 |
Transactional email delivered | com.apsis1.events.transactional-email.delivered | 3 |
Transactional email open | com.apsis1.events.transactional-email.open | 3 |
Transactional email click | com.apsis1.events.transactional-email.click | 3 |
Transactional email abuse | com.apsis1.events.transactional-email.abuse | 3 |
SMS tool
Profile Event | ID | Time to live (years) |
SMS bounce | com.apsis1.events.sms.bounced | 80 |
SMS sent | com.apsis1.events.sms.sent | 3 |
SMS delivered | com.apsis1.events.sms.delivered | 3 |
SMS unsubscribe | com.apsis1.events.sms.unsubscribe | 3 |
SMS click | com.apsis1.events.sms.click | 3 |
Marketing Automation
Profile Event | ID | Time to live |
MA enter | com.apsis1.events.ma.enter | 3 |
MA exit | com.apsis1.events.ma.exit | 3 |
MA achievement | com.apsis1.events.achievement | 3 |
MA move | com.apsis1.events.ma.move | 1 |
MA API trigger | com.apsis1.events.ma.api-trigger | 3 |
Event tool
Profile Event | ID | Time to live (years) |
Event register | com.apsis1.events.event-tool.register | 3 |
Event cancel registration | com.apsis1.events.event-tool.cancel-registration | 3 |
Event invite | com.apsis1.events.event-tool.invite | 3 |
Event check-in | com.apsis1.events.event-tool.check-in | 3 |
Event registration remind | com.apsis1.events.event-tool.remind | 3 |
Event session remind | com.apsis1.events.event-tool.session-remind | 3 |
Event follow-up | com.apsis1.events.event-tool.follow-up | 3 |
Event confirm | com.apsis1.events.event-tool.confirm | 3 |
Manually added attendee | com.apsis1.events.event-tool.manually-added | 3 |
Event delete | com.apsis1.events.event-tool.delete | 3 |
Attendee decline | com.apsis1.events.event-tool.decline | 3 |
Attendee decline all | com.apsis1.events.event-tool.decline-all | 3 |
Guest invite | com.apsis1.events.event-tool.guest-invite | 3 |
In waiting list | com.apsis1.events.event-tool.in-waiting-list | 3 |
Event rating | com.apsis1.events.event-tool.rate | 3 |
Registration source | com.apsis1.events.event-tool.register.collect-* | 3 |
Form and Pages tool
Profile Event | ID | Time to live (years) |
Form SMS | com.apsis1.events.sms.form-consent-submit | 3 |
Form Email | com.apsis1.events.email.form-consent-submit | 3 |
Page view | com.apsis1.events.form-and-page-interactions.pages.view | 1 |
Form view | com.apsis1.events.form-and-page-interactions.forms.view | 1 |
Form start | com.apsis1.events.form-and-page-interactions.forms.start | 1 |
Form submit | com.apsis1.events.form-and-page-interactions.forms.submit-* | 3 |
Form rejected | com.apsis1.events.form-and-page-interactions.forms.reject | 1 |
Form email opt-in | com.apsis1.events.email.optin-confirmation | 3 |
Survey view | com.apsis1.events.survey-interactions.survey.view | 1 |
Survey start | com.apsis1.events.survey-interactions.survey.start | 1 |
Survey | com.apsis1.events.survey-interactions.survey.survey-question-answered | 3 |
Survey response reject
| com.apsis1.events.survey-interactions.survey.reject | 3 |
Survey submit | com.apsis1.events.survey-interactions.survey.submit-* | 3 |
Website tool
Profile Event | ID | Time to live (years) |
Auto collect page view | com.apsis1.events.website.auto-collect.page-view | 1 |
Auto collect google analytics | com.apsis1.events.website.auto-collect.google-analytics | 1 |
Auto collect google analytics seo | com.apsis1.events.website.auto-collect.google-seo | 1 |
Auto collect | com.apsis1.events.website.auto-collect.facebook | 1 |
Auto collect site search | com.apsis1.events.website.auto-collect.site-search | 1 |
Auto collect file download | com.apsis1.events.website.auto-collect.file-download | 1 |
Auto collect external links | com.apsis1.events.website.auto-collect.external-links | 1 |
Auto collects linkdin | com.apsis1.events.website.auto-collect.linkedin | 1 |
Website product collect | com.apsis1.events.website.product.collect-* | 1 |
Website | com.apsis1.events.website.form.collect-* | 1 |
Website conversation basic | com.apsis1.events.website.conversion.basic | 1 |
Website | com.apsis1.events.website.bar.offerclick | 1 |
Website bar submit | com.apsis1.events.website.bar.submit | 1 |
Website bar view | com.apsis1.events.website.bar.view | 1 |
Cookie view | com.apsis1.events.website.cookie.view | 1 |
Cookie submit | com.apsis1.events.website.cookie.submit | 1 |
Website cart | com.apsis1.events.website.cart | 1 |
Website cart product | com.apsis1.events.website.cart.product | 1 |
Website order | com.apsis1.events.website.order | 3 |
Website order product | com.apsis1.events.website.order.product | 3 |
SMS consent submit | com.apsis1.events.sms.consent-submit | 3 |
Email consent submit | com.apsis1.events.email.consent-submit | 3 |
E-commerce
Profile Event | ID | Time to live (years) |
Product purchase | com.apsis1.events.ecom.product-purchase', | 3 |
Product view | com.apsis1.events.ecom.product-view', | 3 |
Cart purchase | com.apsis1.events.ecom.cart-purchase', | 3 |
Product cart | com.apsis1.events.ecom.product-cart', | 1 |
Cart abandon | com.apsis1.events.ecom.cart-abandon', | 1 |
Browse abandon | com.apsis1.events.ecom.browse-abandon' | 1 |
Integrations and One API
Profile Event | ID | Time to live (years) |
Magento wish list product | com.apsis1.integrations.magento.events.wishlist-product | 3 |
Magento product review | com.apsis1.integrations.magento.events.product-review | 3 |
Magento order | com.apsis1.integrations.magento.events.order | 3 |
Magento order product | com.apsis1.integrations.magento.events.order-product | 3 |
Magento subscriber register as customer | com.apsis1.integrations.magento.events.subscriber-register-as-customer | 2 |
Magento customer becomes subscriber | com.apsis1.integrations.magento.events.customer-becomes-subscriber | 2 |
Magento subscriber unsubscribe | com.apsis1.integrations.magento.events.subscriber-unsubscribe | 2 |
Magento product carted | com.apsis1.integrations.magento.events.product-carted | 1 |
Magento abandoned cart | com.apsis1.integrations.magento.events.abandoned-cart | 1 |
Magento abandoned product | com.apsis1.integrations.magento.events.abandoned-product | 1 |
Magento login | com.apsis1.integrations.magento.events.login | 1 |
Playable (LeadFamly) campaign personality | com.apsis1.integrations.leadfamly.events.campaign-personality | 2 |
Playable (LeadFamly) email consent | com.apsis1.events.email.leadfamly.consent | 2 |
Playable (LeadFamly) campaign answers | com.apsis1.integrations.leadfamly.events.campaign-answers | 2 |
Imloyalty custom tags | com.apsis1.integrations.imloyalty.events.custom-tags | 2 |
Imloyalty custom bonus check | com.apsis1.integrations.imloyalty.events.custom-bonus-check | 2 |
Imloyalty custom customer created | com.apsis1.integrations.imloyalty.events.custom-customer-created | 2 |
Imloyalty custom transaction created | com.apsis1.integrations.imloyalty.events.custom-transaction-created | 2 |
Imloyalty custom transactions | com.apsis1.integrations.imloyalty.events.custom-transactions | 2 |
Imloyalty custom transaction row | com.apsis1.integrations.imloyalty.events.custom-transaction-row | 2 |
Tessitura transaction ticket | com.apsis1.integrations.tessitura.events.transaction.ticket | 2 |
Apsis One API Double Opt-in email | com.apsis1.events.email.oneapi-consent-submit | 3 |
Apsis One API Double Opt-in SMS | com.apsis1.events.sms.oneapi-consent-submit | 3 |
Sleeknote email consent | com.apsis1.events.email.sleeknote.consent | 2 |
Common questions
Why do bounces have a much longer TTL than opens or clicks?
Bounce data is kept for 80 years because it directly affects deliverability. We need to remember that an address has bounced repeatedly to keep it suppressed permanently — a key part of protecting your sender reputation.
What happens when an Event reaches its TTL?
The Event is automatically deleted from the profile timeline. The profile itself, its Attributes, and its Tags are unaffected — only the Event record is removed. Segments and reports referencing only the deleted Event will no longer match against it.
Will deleted Events come back if I import the same data again?
No. Once an Event is deleted by TTL, it's gone. New events of the same type can be created going forward, but historical Events that have expired cannot be restored.
Do Custom Events follow the same TTL?
No — Custom Events have no default TTL. You set the lifetime when creating the Event, giving you full control over how long that data is retained.
Can I extend the TTL on an Event?
Yes — TTL settings can be adjusted on a per-account basis. Reach out to Customer Service with details of which Event(s) you'd like adjusted and the new retention period.
Do these TTLs apply to my account if it was created before January 13th 2025?
Accounts created before that date may have different TTL settings. Contact Customer Service if you need to confirm the exact retention applied to your account.