Evergreen tracking methods

This guide explains how the different available tracking methods work.

Tracking methods are used to remember when a visitor started the countdown, so the timer does not restart on every visit.

Cookie

Recognizes the visitor through a cookie in the browser.

When to use it

This is the recommended choice for most cases.

Advantages

  • simple;
  • suitable for landing pages and standard offers;
  • does not link the timer to the IP address.

Limitations

  • if the user deletes cookies, the timer may restart;
  • if the user changes browser, the timer may restart;
  • in private browsing, the behavior may not be persistent.

IP

Recognizes the visitor through an anonymized IP address.

When to use it

Use it when you want to reduce resets caused by cookie deletion.

Advantages

  • more resistant to cookie deletion;
  • useful in contexts where the cookie alone may not be enough.

Limitations

  • users on the same network may share the same timer;
  • if the user changes network or IP address, the timer may restart.

Cookie or IP

Combines cookie and IP.

When to use it

Use it when you want tracking that is more persistent than cookie-only tracking.

Behavior

  • if only the IP record exists, the cookie is created or aligned;
  • if only the cookie record exists, the IP record is created or aligned;
  • if both exist, the oldest timestamp is used.

Advantages

  • more resistant to intentional resets;
  • useful for stricter evergreen offers.

Limitations

  • users on the same network may share the same state;
  • it may be less individual than cookie-only tracking.

Logged-in user

Associates the timer with the WordPress account of the logged-in user.

When to use it

Use it for private areas, memberships, courses, user portals, and funnels with login.

Advantages

  • follows the user even if they change browser;
  • does not depend on IP or cookies;
  • it is the most consistent method when the user’s identity is known.

Limitations

  • it works as user tracking only if the user is logged in;
  • if the visitor is not logged in, the plugin uses the cookie as a fallback.

When an Evergreen timer can restart from the beginning

An Evergreen timer can restart when the plugin can no longer link the visitor to the existing tracking data.

This can happen if:

  • the visitor deletes cookies;
  • the cookie expires;
  • they change browser;
  • they change network or IP address;
  • the countdown ID is changed;
  • the countdown is duplicated;
  • the tracking data is cleaned up because it has expired.

Practical warning

To keep an already published Evergreen timer stable, avoid changing the countdown ID and tracking method.