Set a virtual fence through the instructions for your actual tracker service, then check the boundary's active state and your phone's notification permissions separately. A saved shape on a map does not show that a boundary alert reached your phone. It also does not physically contain a pet.

This guide uses three current Tractive help documents from one publisher. It describes their mobile-app workflow, including an unresolved disagreement about rectangular minimum size. Other services and different app views need their own matching instructions.

Identify the tracker and the boundary you intend to create

Select the intended tracker before working on its settings. If an account contains several devices, check its identifier or other documented identification rather than relying only on a nickname. This is a setting for the selected service and device, not a boundary attached to the physical collar itself.

Decide what location you want to describe and give it a name you can recognize later. Keep your intended area separate from what the app will accept and display. A property line, garden edge or road on a map is not, by itself, a verified notification boundary.

Follow Tractive's creation path and review Active separately

Tractive's Virtual Fence guide describes these mobile-app steps:

  1. On Map, tap the plus icon, then Add Virtual Fence.
  2. Choose Safe Zone or No-Go Zone, then a type such as Home or Park.
  3. Customize the shape and size, continue and name the fence.
  4. Review the settings and select Create.

The guide cautions against overlapping fences. It also gives a separate management path: Profile → Safety & Location → Virtual Fences. Select the fence, check the Active switch and save any intended change. A deactivated fence does not produce its alerts.

Safe Zone and No-Go Zone are service labels for digital areas. They do not certify that a place is safe or that a pet cannot enter or leave it.

Leave the conflicting size requirement unresolved

The creation guide lists a rectangular minimum of 100 m², while Tractive's dedicated minimum-size article and its diagram say 100 × 100 m. These are different requirements.

The dedicated article also explains that small boundaries and less accurate indoor positions can contribute to false notifications. A Power Saving Zone is not simply another name for an active virtual fence.

Keep that uncertainty with the setting rather than hiding it behind a “setup complete” note. Do not replace the maker's unresolved dimensions with a guessed garden-sized boundary or a measurement borrowed from another brand.

Check the phone's permission layer

Tractive's notification troubleshooting page starts with app permissions. It describes Account → Notifications → Enable Notifications, followed by the applicable phone permission. Its iOS route opens the phone's app settings to allow notifications; its Android route uses an Allow prompt.

The same page lists phone internet access, Do Not Disturb or Focus settings, battery optimization and third-party blocking among possible delivery issues. Use the instructions matching your phone. Allowing notifications is a permission change, not proof that a particular boundary alert was delivered.

If the view differs, note the phone platform, app view and exact message before asking support. Do not keep changing unrelated settings until a button happens to resemble an old screenshot.

Record the setting and the observation as different results

A useful completion note identifies the tracker, fence name and type, displayed shape, Active state, phone permission and any unresolved size question. If an alert has actually arrived during ordinary use, record that observation separately. Do not substitute “created a fence” for “received an alert,” or interpret no alert as proof that no crossing occurred.

This guide has not operated an account, staged a pet crossing or tested notification delivery. For the separate location-to-phone connection, read how pet GPS trackers work. When comparing cellular GPS pet trackers, check each exact service's documented boundary features.