Overview
The integration works in two stages:
Camera-side — Verify ONVIF is active, configure detection zones using AXIS Object Analytics, and enable the Axis video motion tracker in the camera's Metadata Configuration.
Server-side — Register the camera with the correct stream URLs, then add or update a channel to receive the analytics stream.
Part 1 — Camera Configuration
1.1 Access the Camera Web Interface
Open a browser and navigate to the camera's IP address (e.g.
http://192.168.1.100).Log in with your administrator credentials.
If this is the first time accessing the camera, follow the initial setup wizard to set a password.
Tip: You can find the camera's IP using the AXIS IP Utility or AXIS Device Manager tools available from Axis Communications.
1.2 Verify ONVIF is Active
Axis cameras come with an ONVIF account enabled by default. You do not need to create a new one — just confirm the service is active.
Go to System → ONVIF.
Confirm the ONVIF service is enabled. If there is an Enable ONVIF toggle, make sure it is turned on.
Verify that at least one ONVIF user exists in the list.
Note: The ONVIF account is used by the server to communicate with the camera. You do not need to configure media profiles manually — this is handled automatically through the Corvid web interface.
1.3 Install and Enable AXIS Object Analytics
AXIS Object Analytics is the application used to configure motion detection and define detection zones.
Check if already installed:
Go to Apps in the camera menu.
Look for AXIS Object Analytics in the list.
If present, ensure it is toggled On.
If not installed:
Go to Apps → Add app.
Search for AXIS Object Analytics.
Click Install, then toggle it On once installed.
Compatibility: AXIS Object Analytics requires cameras with an ARTPEC-7 or ARTPEC-8 chip or newer. If your camera does not support it, check if AXIS Video Motion Detection 4 is available as an alternative.
1.4 Configure Detection Scenarios
Open AXIS Object Analytics from the Apps menu.
Click + Add scenario.
Choose a scenario type — for most motion detection use cases, select Motion in area.
Under Trigger conditions, select the object types to detect (e.g. Humans, Vehicles).
1.5 Draw Detection Zones (Polygons)
The analytics stream uses polygon zones — you must define these on the camera before the server can receive motion events.
In the scenario editor, locate the Include area section on the camera view.
Click Draw area or Edit area.
Click to place polygon vertices around the region you want to monitor. Close the polygon by clicking the first point again.
To add exclude zones (areas to ignore), use the Exclude area option and draw additional polygons.
Give the scenario a clear name (e.g.
Zone 1 - Entrance).Click Save.
For multi-lens cameras: Repeat this process for each lens/channel that requires analytics.
1.6 Enable Axis Video Motion Tracker in Metadata Configuration
This step activates the motion tracking metadata stream that the server listens to.
In the camera web interface, go to Analytics → Metadata Configuration.
Locate Axis video motion tracker in the list.
Enable it for the camera you want to activate — if the camera is multi-lens, enable it per lens as needed.
Save the configuration.
Note: Without this step, the analytics channel on the server will not receive motion events even if the detection zones are correctly configured.
1.7 Verify Detection is Working
Before proceeding to server configuration, confirm analytics are firing correctly:
Stay in AXIS Object Analytics and observe the live view.
Trigger movement within the defined polygon zone.
Confirm that the event indicator activates.
If nothing triggers, revisit the zone boundaries and object type filters.
Part 2 — Server Configuration
2.1 Create the Camera Object
Register the camera on the server by creating a camera object and linking it with the appropriate stream URLs.
Follow the Create Camera guide.
2.2 Add the Analytics Stream Channel
Once the camera is created and streaming, configure the analytics channel. You can either create a new channel or update an existing one.
Important: The axis-media path requires Media account credentials — not ONVIF credentials. Make sure you are using your Axis Media account login when configuring this channel.
The analytics stream URL format is:
axis-media/media.amp?analytics=polygon&videocodec=h264&resolution=1920x1080
For multi-lens cameras, add the camera parameter to specify the lens:
axis-media/media.amp?camera={camera number}&analytics=polygon&videocodec=h264&resolution=1920x1080Multi-lens example (camera 3):
axis-media/media.amp?camera=3&analytics=polygon&videocodec=h264&resolution=1920x1080
Replace camera=3 with the actual lens number. For single-lens cameras, omit the camera parameter entirely.
Option A — Create a New Analytics Channel
In the Web App, navigate to the camera details by clicking on the camera item.
Navigate to the Settings tab and scroll down to the Channels section.
Click Add Channel.
Enter a channel name.
Paste the analytics stream URL for this camera.
Apply the changes.
Option B — Update a Pre-configured Channel
In the Web App, navigate to the camera details by clicking on the camera item.
Navigate to the Settings tab and scroll down to the Channels section.
Update the existing channel by replacing the stream URL with the analytics stream URL.
Apply the changes.
2.3 Verify the Analytics Integration
After saving the analytics channel, confirm the channel is streaming by selecting it on the player playlist.
Trigger movement within the polygon zone you defined in step 1.5.
Confirm that motion events are received and appear correctly in the platform.
URL Parameter Reference
Parameter | Description | Example |
| Lens number (multi-lens cameras only) |
|
| Analytics type |
|
| Video encoding format |
|
| Stream resolution |
|
Troubleshooting
Camera not connecting after registration
Verify the camera IP is reachable from the server.
Confirm ONVIF is enabled and active (step 1.2).
Analytics channel not receiving events
Ensure AXIS Object Analytics is running and the scenario is active (step 1.3).
Confirm the polygon zone is correctly drawn and covers the intended area (step 1.5).
Verify that Axis video motion tracker is enabled in Analytics → Metadata Configuration (step 1.6).
Confirm you are using Media credentials (not ONVIF credentials) for the
axis-mediastream URL.Verify the
camera=parameter matches the correct lens number for multi-lens cameras.
Multi-lens cameras showing wrong feed
Double-check the
camera=value in the analytics URL against the lens numbering in the camera's web interface.
AXIS Object Analytics not available
Confirm the camera model supports ARTPEC-7 or ARTPEC-8 or newer.
If not supported, check for AXIS Video Motion Detection 4 under Apps as an alternative.