{
    "api_version": "1",
    "kind": "dse_post",
    "self": "https://update.dsesecurity.com/api/v1/posts/allow-for-axis-tracking-filters-before-expecting-an-event/",
    "item": {
        "id": "https://update.dsesecurity.com/updates/allow-for-axis-tracking-filters-before-expecting-an-event/",
        "slug": "allow-for-axis-tracking-filters-before-expecting-an-event",
        "url": "https://update.dsesecurity.com/updates/allow-for-axis-tracking-filters-before-expecting-an-event/",
        "alternate_urls": {
            "markdown": "https://update.dsesecurity.com/updates/allow-for-axis-tracking-filters-before-expecting-an-event.md",
            "json": "https://update.dsesecurity.com/api/v1/posts/allow-for-axis-tracking-filters-before-expecting-an-event/"
        },
        "title": "Allow for Axis tracking filters before expecting an event",
        "summary": "Allow for Axis Digital Autotracking’s configured ignore-filter qualification before expecting an event. Review short-lived-object timing and required recording pre-trigger coverage as separate acceptance decisions.",
        "format": {
            "slug": "guide",
            "name": "Guide"
        },
        "priority": {
            "slug": "advisory",
            "name": "Advisory"
        },
        "featured": false,
        "image": {
            "theme": "physical-security",
            "label": "Physical security",
            "alt": "Integrated video surveillance and controlled entry at a modern commercial facility.",
            "card_url": "https://update.dsesecurity.com/assets/editorial/physical-security-card.webp?v=1.8.20",
            "hero_url": "https://update.dsesecurity.com/assets/editorial/physical-security-hero.webp?v=1.8.20",
            "social_url": "https://update.dsesecurity.com/assets/editorial/physical-security-social-v2.jpg?v=1.8.20",
            "width": 2400,
            "height": 1350
        },
        "topics": [
            {
                "slug": "it",
                "name": "IT",
                "url": "https://update.dsesecurity.com/topic/it/"
            },
            {
                "slug": "video-surveillance",
                "name": "Video Surveillance",
                "url": "https://update.dsesecurity.com/topic/video-surveillance/"
            }
        ],
        "author": {
            "name": "DSE Security Editorial Team",
            "url": "https://update.dsesecurity.com/#editorial-team",
            "type": "Organization"
        },
        "publisher": {
            "name": "Detection Systems & Engineering",
            "url": "https://dsesecurity.com/"
        },
        "published_at": "2026-10-29T20:33:15+00:00",
        "modified_at": "2026-10-29T20:33:34+00:00",
        "reviewed_on": "2026-10-29",
        "reading_minutes": 3,
        "word_count": 514,
        "potentially_affected": "Axis products exposing the documented Digital autotracking API interface; confirm actual device, hardware and software applicability before applying the proposed checks.",
        "dse_recommendation": "DSE recommends comparing object motion, filter qualification, event time and retrieved recording context as separate evidence.",
        "primary_source": {
            "name": "Axis Communications — Digital autotracking API",
            "url": "https://developer.axis.com/vapix/applications/digital-autotracking-api/",
            "published_on": null,
            "authority": "Axis Communications"
        },
        "publishing_principles": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/",
        "usage_info": "https://update.dsesecurity.com/usage/",
        "copyright_notice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.",
        "content_html": "<p><strong>Bottom line:</strong> Write the expected qualification delay before diagnosing a missing tracking event. Compare the permitted object’s actual movement with the configured filter and the event timeline, then inspect any required recording context separately.</p>\n<h2>Source fact: documented behavior</h2>\n<p>Axis’s <a href=\"https://developer.axis.com/vapix/applications/digital-autotracking-api/\" target=\"_blank\" rel=\"noopener noreferrer\">Digital autotracking API</a> says ignore-filter conditions must be evaluated and satisfied before tracking begins and an event is emitted.</p>\n<p>For the short-lived-object <code>Time</code> filter, an object must still be moving after the configured interval; tracking and its event are delayed by that interval.</p>\n<p>The page requires Digital Autotracking 2 or later for its short-lived-object filter and recommends recording pre-trigger coverage when a delayed event starts recording.</p>\n<h2>What the source does not establish</h2>\n<p>Do not infer equivalent filter behavior for a different analytics application or a guarantee that every moving object will qualify. Confirm application version, camera support and the exact configured areas and filters. A tracking event alone does not establish the required recorded lead-in, classification accuracy or complete detection coverage.</p>\n<h2>Applicability questions</h2>\n<ul>\n<li>Does the actual application version support the configured filter?</li>\n<li>Which filter interval and scene region are being assessed?</li>\n<li>How long should each approved test object remain moving?</li>\n<li>What pre-event context must the recording owner be able to retrieve?</li>\n</ul>\n<h2>DSE recommendation: controlled next steps</h2>\n<p><em>The following steps are DSE recommendations based on the cited source.</em></p>\n<p>DSE recommends comparing object motion, filter qualification, event time and retrieved recording context as separate evidence.</p>\n<ol>\n<li>Read the actual application configuration and identify the supported short-lived-object filter and its value. Review the intended include and exclude areas with the operator. Write a proposed harmless short appearance and a longer permitted movement as distinct cases, choosing the paths and timing under the site’s approved test conditions rather than inventing a universal threshold.</li>\n<li>Observe the two cases with authorized participants or harmless controlled inputs. Preserve the movement timeline and corresponding tracking-event observations. Keep the short case’s disposition separate from a communication failure. Investigate a longer qualifying-looking case with the actual configured filters and consumer evidence before disabling several nuisance controls together.</li>\n<li>Where the event starts recording, have the recording owner review the supported pre-trigger setup against the required lead-in. Retrieve the relevant test interval through the normal authorized client and inspect the earlier movement independently. Leave insufficient context as a recording requirement to resolve rather than describing a later event bookmark as proof that the whole approach was retained.</li>\n</ol>\n<h2>Verification and evidence</h2>\n<p>Retain the application/version reference, areas, filter settings, proposed case definitions, actual motion and event timeline, and the permitted recording observation. Have a reviewer distinguish a configured qualification delay from an independently demonstrated message-path failure. Keep unexpected misses and nuisance events visible to the owner.</p>\n<p>Use a proposed desk case where an investigator needs activity before the tracking event. Require an explicit pre-trigger and retrieval decision, without promising a fixed retention duration. No object was tracked, analytics accuracy measured or recording retrieved during preparation of this article.</p>\n<h2>Official references</h2>\n<ul>\n<li><a href=\"https://developer.axis.com/vapix/applications/digital-autotracking-api/\" target=\"_blank\" rel=\"noopener noreferrer\">Digital autotracking API</a> — Axis Communications; official VAPIX documentation.</li>\n</ul>\n<p>Source review completed October 29, 2026. Recheck the official documentation and the deployed device’s capabilities before changing production settings.</p>\n",
        "content_text": "Bottom line: Write the expected qualification delay before diagnosing a missing tracking event. Compare the permitted object’s actual movement with the configured filter and the event timeline, then inspect any required recording context separately.\nSource fact: documented behavior\nAxis’s Digital autotracking API says ignore-filter conditions must be evaluated and satisfied before tracking begins and an event is emitted.\nFor the short-lived-object Time filter, an object must still be moving after the configured interval; tracking and its event are delayed by that interval.\nThe page requires Digital Autotracking 2 or later for its short-lived-object filter and recommends recording pre-trigger coverage when a delayed event starts recording.\nWhat the source does not establish\nDo not infer equivalent filter behavior for a different analytics application or a guarantee that every moving object will qualify. Confirm application version, camera support and the exact configured areas and filters. A tracking event alone does not establish the required recorded lead-in, classification accuracy or complete detection coverage.\nApplicability questions\n\nDoes the actual application version support the configured filter?\nWhich filter interval and scene region are being assessed?\nHow long should each approved test object remain moving?\nWhat pre-event context must the recording owner be able to retrieve?\n\nDSE recommendation: controlled next steps\nThe following steps are DSE recommendations based on the cited source.\nDSE recommends comparing object motion, filter qualification, event time and retrieved recording context as separate evidence.\n\nRead the actual application configuration and identify the supported short-lived-object filter and its value. Review the intended include and exclude areas with the operator. Write a proposed harmless short appearance and a longer permitted movement as distinct cases, choosing the paths and timing under the site’s approved test conditions rather than inventing a universal threshold.\nObserve the two cases with authorized participants or harmless controlled inputs. Preserve the movement timeline and corresponding tracking-event observations. Keep the short case’s disposition separate from a communication failure. Investigate a longer qualifying-looking case with the actual configured filters and consumer evidence before disabling several nuisance controls together.\nWhere the event starts recording, have the recording owner review the supported pre-trigger setup against the required lead-in. Retrieve the relevant test interval through the normal authorized client and inspect the earlier movement independently. Leave insufficient context as a recording requirement to resolve rather than describing a later event bookmark as proof that the whole approach was retained.\n\nVerification and evidence\nRetain the application/version reference, areas, filter settings, proposed case definitions, actual motion and event timeline, and the permitted recording observation. Have a reviewer distinguish a configured qualification delay from an independently demonstrated message-path failure. Keep unexpected misses and nuisance events visible to the owner.\nUse a proposed desk case where an investigator needs activity before the tracking event. Require an explicit pre-trigger and retrieval decision, without promising a fixed retention duration. No object was tracked, analytics accuracy measured or recording retrieved during preparation of this article.\nOfficial references\n\nDigital autotracking API — Axis Communications; official VAPIX documentation.\n\nSource review completed October 29, 2026. Recheck the official documentation and the deployed device’s capabilities before changing production settings.",
        "content_markdown": "Bottom line: Write the expected qualification delay before diagnosing a missing tracking event. Compare the permitted object’s actual movement with the configured filter and the event timeline, then inspect any required recording context separately.\n\n## Source fact: documented behavior\n\nAxis’s [Digital autotracking API](https://developer.axis.com/vapix/applications/digital-autotracking-api/) says ignore-filter conditions must be evaluated and satisfied before tracking begins and an event is emitted.\n\nFor the short-lived-object Time filter, an object must still be moving after the configured interval; tracking and its event are delayed by that interval.\n\nThe page requires Digital Autotracking 2 or later for its short-lived-object filter and recommends recording pre-trigger coverage when a delayed event starts recording.\n\n## What the source does not establish\n\nDo not infer equivalent filter behavior for a different analytics application or a guarantee that every moving object will qualify. Confirm application version, camera support and the exact configured areas and filters. A tracking event alone does not establish the required recorded lead-in, classification accuracy or complete detection coverage.\n\n## Applicability questions\n\n- Does the actual application version support the configured filter?\n\n- Which filter interval and scene region are being assessed?\n\n- How long should each approved test object remain moving?\n\n- What pre-event context must the recording owner be able to retrieve?\n\n## DSE recommendation: controlled next steps\n\nThe following steps are DSE recommendations based on the cited source.\n\nDSE recommends comparing object motion, filter qualification, event time and retrieved recording context as separate evidence.\n\n- Read the actual application configuration and identify the supported short-lived-object filter and its value. Review the intended include and exclude areas with the operator. Write a proposed harmless short appearance and a longer permitted movement as distinct cases, choosing the paths and timing under the site’s approved test conditions rather than inventing a universal threshold.\n\n- Observe the two cases with authorized participants or harmless controlled inputs. Preserve the movement timeline and corresponding tracking-event observations. Keep the short case’s disposition separate from a communication failure. Investigate a longer qualifying-looking case with the actual configured filters and consumer evidence before disabling several nuisance controls together.\n\n- Where the event starts recording, have the recording owner review the supported pre-trigger setup against the required lead-in. Retrieve the relevant test interval through the normal authorized client and inspect the earlier movement independently. Leave insufficient context as a recording requirement to resolve rather than describing a later event bookmark as proof that the whole approach was retained.\n\n## Verification and evidence\n\nRetain the application/version reference, areas, filter settings, proposed case definitions, actual motion and event timeline, and the permitted recording observation. Have a reviewer distinguish a configured qualification delay from an independently demonstrated message-path failure. Keep unexpected misses and nuisance events visible to the owner.\n\nUse a proposed desk case where an investigator needs activity before the tracking event. Require an explicit pre-trigger and retrieval decision, without promising a fixed retention duration. No object was tracked, analytics accuracy measured or recording retrieved during preparation of this article.\n\n## Official references\n\n- [Digital autotracking API](https://developer.axis.com/vapix/applications/digital-autotracking-api/) — Axis Communications; official VAPIX documentation.\n\nSource review completed October 29, 2026. Recheck the official documentation and the deployed device’s capabilities before changing production settings."
    },
    "json_ld": {
        "@context": "https://schema.org",
        "@graph": [
            {
                "@type": "Organization",
                "@id": "https://dsesecurity.com/#organization",
                "name": "Detection Systems & Engineering",
                "alternateName": "DSE Security",
                "url": "https://dsesecurity.com/",
                "logo": {
                    "@type": "ImageObject",
                    "url": "https://update.dsesecurity.com/assets/dse-logo-20260812.png?v=1.8.20"
                }
            },
            {
                "@type": "Organization",
                "@id": "https://update.dsesecurity.com/#editorial-team",
                "name": "DSE Security Editorial Team",
                "url": "https://update.dsesecurity.com/",
                "parentOrganization": {
                    "@id": "https://dsesecurity.com/#organization"
                }
            },
            {
                "@type": "WebSite",
                "@id": "https://update.dsesecurity.com/#website",
                "name": "DSE Updates",
                "alternateName": "DSE Security Knowledge Hub",
                "url": "https://update.dsesecurity.com/",
                "inLanguage": "en-US",
                "publisher": {
                    "@id": "https://dsesecurity.com/#organization"
                },
                "potentialAction": {
                    "@type": "SearchAction",
                    "target": {
                        "@type": "EntryPoint",
                        "urlTemplate": "https://update.dsesecurity.com/?q={search_term_string}"
                    },
                    "query-input": "required name=search_term_string"
                }
            },
            {
                "@type": "WebPage",
                "@id": "https://update.dsesecurity.com/updates/allow-for-axis-tracking-filters-before-expecting-an-event/",
                "url": "https://update.dsesecurity.com/updates/allow-for-axis-tracking-filters-before-expecting-an-event/",
                "isPartOf": {
                    "@id": "https://update.dsesecurity.com/#website"
                },
                "lastReviewed": "2026-10-29"
            },
            {
                "@type": "BreadcrumbList",
                "@id": "https://update.dsesecurity.com/updates/allow-for-axis-tracking-filters-before-expecting-an-event/#breadcrumbs",
                "itemListElement": [
                    {
                        "@type": "ListItem",
                        "position": 1,
                        "name": "DSE Updates",
                        "item": "https://update.dsesecurity.com/"
                    },
                    {
                        "@type": "ListItem",
                        "position": 2,
                        "name": "IT",
                        "item": "https://update.dsesecurity.com/topic/it/"
                    },
                    {
                        "@type": "ListItem",
                        "position": 3,
                        "name": "Allow for Axis tracking filters before expecting an event",
                        "item": "https://update.dsesecurity.com/updates/allow-for-axis-tracking-filters-before-expecting-an-event/"
                    }
                ]
            },
            {
                "@type": [
                    "Article",
                    "TechArticle"
                ],
                "@id": "https://update.dsesecurity.com/updates/allow-for-axis-tracking-filters-before-expecting-an-event/#article",
                "identifier": "https://update.dsesecurity.com/updates/allow-for-axis-tracking-filters-before-expecting-an-event/",
                "url": "https://update.dsesecurity.com/updates/allow-for-axis-tracking-filters-before-expecting-an-event/",
                "headline": "Allow for Axis tracking filters before expecting an event",
                "description": "Allow for Axis Digital Autotracking’s configured ignore-filter qualification before expecting an event.",
                "abstract": "Allow for Axis Digital Autotracking’s configured ignore-filter qualification before expecting an event. Review short-lived-object timing and required recording pre-trigger coverage as separate acceptance decisions.",
                "articleBody": "Bottom line: Write the expected qualification delay before diagnosing a missing tracking event. Compare the permitted object’s actual movement with the configured filter and the event timeline, then inspect any required recording context separately.\nSource fact: documented behavior\nAxis’s Digital autotracking API says ignore-filter conditions must be evaluated and satisfied before tracking begins and an event is emitted.\nFor the short-lived-object Time filter, an object must still be moving after the configured interval; tracking and its event are delayed by that interval.\nThe page requires Digital Autotracking 2 or later for its short-lived-object filter and recommends recording pre-trigger coverage when a delayed event starts recording.\nWhat the source does not establish\nDo not infer equivalent filter behavior for a different analytics application or a guarantee that every moving object will qualify. Confirm application version, camera support and the exact configured areas and filters. A tracking event alone does not establish the required recorded lead-in, classification accuracy or complete detection coverage.\nApplicability questions\n\nDoes the actual application version support the configured filter?\nWhich filter interval and scene region are being assessed?\nHow long should each approved test object remain moving?\nWhat pre-event context must the recording owner be able to retrieve?\n\nDSE recommendation: controlled next steps\nThe following steps are DSE recommendations based on the cited source.\nDSE recommends comparing object motion, filter qualification, event time and retrieved recording context as separate evidence.\n\nRead the actual application configuration and identify the supported short-lived-object filter and its value. Review the intended include and exclude areas with the operator. Write a proposed harmless short appearance and a longer permitted movement as distinct cases, choosing the paths and timing under the site’s approved test conditions rather than inventing a universal threshold.\nObserve the two cases with authorized participants or harmless controlled inputs. Preserve the movement timeline and corresponding tracking-event observations. Keep the short case’s disposition separate from a communication failure. Investigate a longer qualifying-looking case with the actual configured filters and consumer evidence before disabling several nuisance controls together.\nWhere the event starts recording, have the recording owner review the supported pre-trigger setup against the required lead-in. Retrieve the relevant test interval through the normal authorized client and inspect the earlier movement independently. Leave insufficient context as a recording requirement to resolve rather than describing a later event bookmark as proof that the whole approach was retained.\n\nVerification and evidence\nRetain the application/version reference, areas, filter settings, proposed case definitions, actual motion and event timeline, and the permitted recording observation. Have a reviewer distinguish a configured qualification delay from an independently demonstrated message-path failure. Keep unexpected misses and nuisance events visible to the owner.\nUse a proposed desk case where an investigator needs activity before the tracking event. Require an explicit pre-trigger and retrieval decision, without promising a fixed retention duration. No object was tracked, analytics accuracy measured or recording retrieved during preparation of this article.\nOfficial references\n\nDigital autotracking API — Axis Communications; official VAPIX documentation.\n\nSource review completed October 29, 2026. Recheck the official documentation and the deployed device’s capabilities before changing production settings.",
                "datePublished": "2026-10-29T20:33:15+00:00",
                "dateModified": "2026-10-29T20:33:34+00:00",
                "mainEntityOfPage": {
                    "@id": "https://update.dsesecurity.com/updates/allow-for-axis-tracking-filters-before-expecting-an-event/"
                },
                "inLanguage": "en-US",
                "isAccessibleForFree": true,
                "author": {
                    "@type": "Organization",
                    "name": "DSE Security Editorial Team",
                    "url": "https://update.dsesecurity.com/#editorial-team"
                },
                "publisher": {
                    "@id": "https://dsesecurity.com/#organization"
                },
                "image": {
                    "@type": "ImageObject",
                    "@id": "https://update.dsesecurity.com/updates/allow-for-axis-tracking-filters-before-expecting-an-event/#primaryimage",
                    "url": "https://update.dsesecurity.com/assets/editorial/physical-security-social-v2.jpg?v=1.8.20",
                    "contentUrl": "https://update.dsesecurity.com/assets/editorial/physical-security-social-v2.jpg?v=1.8.20",
                    "width": 1200,
                    "height": 630,
                    "caption": "Allow for Axis tracking filters before expecting an event"
                },
                "articleSection": [
                    "IT",
                    "Video Surveillance"
                ],
                "keywords": [
                    "IT",
                    "Video Surveillance",
                    "Guide",
                    "Advisory priority"
                ],
                "genre": "Guide",
                "about": [
                    {
                        "@type": "Thing",
                        "name": "IT",
                        "url": "https://update.dsesecurity.com/topic/it/"
                    },
                    {
                        "@type": "Thing",
                        "name": "Video Surveillance",
                        "url": "https://update.dsesecurity.com/topic/video-surveillance/"
                    }
                ],
                "wordCount": 514,
                "timeRequired": "PT3M",
                "publishingPrinciples": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/",
                "usageInfo": "https://update.dsesecurity.com/usage/",
                "copyrightHolder": {
                    "@id": "https://dsesecurity.com/#organization"
                },
                "copyrightNotice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.",
                "citation": {
                    "@type": "CreativeWork",
                    "name": "Axis Communications — Digital autotracking API",
                    "url": "https://developer.axis.com/vapix/applications/digital-autotracking-api/"
                }
            }
        ]
    }
}