Bulk Video Status Manager

How to Create a Bulk Video Status Manager Automation Script

The Bulk Video Status Manager is a spreadsheet script that makes changing platform-level resource settings simpler than ever. Simply provide all necessary data in an organized worksheet, and the script takes care of everything for you!

Inventory management for bulk film gear involves tracking equipment purchased in large quantities to ensure smooth operations, reduced risks and costs, and maximized profits.

How it works

Video Status Manager makes it possible to set up automated workflows that turn a CSV file of video files into different variations, with captions and hosting, that you can upload. Workflows can be initiated either via CSV or webhook; CSV is a text file using commas as delimiters that allows bulk editing videos or can list URLs that trigger uploads; webhooks provide another way of automating video creation based on events like someone signing up for your newsletter.

Start off by selecting Bulk Video Status Manager from My Tools menu, then click Start to begin creating and running a workflow. A window will appear where you can upload CSV file(s). When that file(s) have been uploaded, your workflow will begin and update video status in Wiki accordingly.

Set your Video Transcode Profile so it automatically applies to each video in a batch. These profiles contain options to control how video conversion happens, such as codec selection and bit rate settings, but also feature advanced settings that may help customize conversion further, like key frame usage (more key frames will improve navigation within video files, but may increase file sizes).

Once a video has been processed by the Video Transcode Profile, its status will change to Completed with a link leading to its final output file. You can track its progress using Workflows by visiting their Jobs tab; each job will display Job ID, time taken and video status being processed.

Configure a Video Captioning Profile to automatically generate captions for every video in a batch. Generated captions will be saved as Video Text Track (VTT) files with their names containing an appended language label; this feature requires Amplience credits at an hourly rate; for every minute spent creating captions this feature charges 5 credits.

Getting Started

Once all the video files that need editing have been added to a spreadsheet, it’s time to begin creating your automation script. To do so, authenticate it with your API key and prepare a payload of information to send to FastPix containing variables specific to each video – such as intro and outro URLs, timestamps, metadata – as well as reference to where this data resides in your spreadsheet.

Video transcoding profiles are conversion settings designed to convert source videos into optimized and compatible versions for various platforms, devices and viewers. When selecting a video from Media Library, click the plus icon to add transcoding profiles; alternatively you can apply one manually after uploading it to Content Hub.

When the Amplience Caption Generation feature is enabled, when applying a captioning profile to a video file in Content Hub, the system checks your Amplience credit balance for sufficient credits to complete transcription and create VTT (video text track) files corresponding to each VTT language selected for captions generation. Once generated captions have been saved in video files according to an naming convention that includes them;

As the profile runs, its encoding status will display a progress bar to show its progress. Once complete, its status will change to indicate it has successfully encoded and that a VTT (video text track) file has been generated.

Once your video is finished, you can view it through Content Hub by selecting its file and pressing Play. Alternatively, use Download to save a copy on your device.

With the aid of a simple workflow, it’s quick and easy to create multiple YouTube Shorts in rapid succession for use as part of a campaign. This method of automation works best when used for similar videos that fall under promotional or educational categories; its construction is straightforward and allows any user to automate complex processes without needing to write one line of code.

Setting up triggers

Triggers are the conditions that initiate automations. They determine whether contacts become eligible to move through your workflow you created, enabling multiple triggering conditions to set off one automation.

To create a trigger, choose it from the list and fill in all the required information. You can choose to enable or disable it and give it a name; additionally, when its condition is met you can specify actions to be triggered when that condition has been fulfilled, for instance selecting ticket type or email notification as appropriate.

Notifications allow you to stay informed of changes to the status or data collected by sensors, using either PRTG’s web interface, email or smartphone apps (depending on device). Notification settings can be defined within an object higher in its hierarchy – those inheriting notification triggers appear under Notification Triggers tab in each object that inherits them.

Sensor triggers allow you to set conditions and latency settings that determine when sensors change status and trigger notifications, as well as specify how long PRTG waits before sending notifications–this helps avoid unnecessary alarms.

The table below details all available triggers for each plan, noting that some have specific features or restrictions depending on which plan was selected.

Custom object field change A custom object field change triggered an automation when one of your specified fields in a custom object changes from one value to another. You can set both starting and target values, as well as include conditions that exclude certain types of values from consideration.

An order abandons

This trigger starts an automation when someone abandons their cart on your connected ecommerce store, with options to set parameters such as number of items in cart and total value as well as other parameters.

The “Mandatory field mark” setting allows you to specify which fields should be included in this trigger’s criteria. Use Greater than, Less Than or Is not empty filters to narrow your selection.

Managing triggers

GTM’s Bulk Trigger Action feature is an invaluable asset to brands with multiple product videos to track. Team admins can utilize it to quickly change multiple PM triggers at the same time instead of going through each trigger individually.

To use it, navigate to GTM’s Tags section and check all of the boxes whose triggers you wish to update. When finished, click on the funky trigger icon in the table header for an overlay to open; widescreen monitor users will also have this handy visual reminder showing just how many items they’ve selected (see image below).

By clicking on either the triggers or exceptions list in the bulk action overlay and clicking on the blue plus sign, you enter into the usual trigger and exception creation process and can edit a complete PM trigger set including all its conditions in bulk.

This process will replace any custom tags you had installed to trigger PM workflows and update any dataLayer variables associated with them – for instance, an event tag might be created specifically to send video-related data back to Google Analytics.

Example: Imagine setting up a custom Google Analytics event that tracks how much of a video each viewer watches; then building out a workflow to nurture leads based on how long they spent watching, sending follow-up emails or offering additional resources as appropriate.

Custom Events You Create will contain three main filters: Time, Percentage and Total Time Watched. A timeline filter will trigger an event once a viewer reaches a particular percentage mark (e.g. 25%, 50% or 75% watched); percentage thresholds trigger events regardless of whether a viewer watched continuously from start to finish of video timeline.

Once your new PM triggers have been configured, they can be deployed via Solution Manager in seconds to their final environment. You should then test them in live environments to make sure everything is functioning as expected and identify and resolve any potential issues by creating comprehensive test classes and redeploying triggers if necessary.