Processing, encoding, uploading, embedding, and sending… Do these words make you cringe?
We know they do, it’s one of the reasons why we’re in business! These are just a few components in the full process of not only sending your videos to customers, but making them look good as well. We handle all of this technical dirty work so you can focus on selling. But what is the dirty work? What actually happens to your video behind the scenes?
Come with us on your video journey and check out all of the technical things you’ll never, ever, have to worry about!
So you’ve recorded your video, entered your customer’s information, and hit ‘send’ in the Authntk app, here’s what happens next…
1. Your video is automatically saved in your photo library on your device.
2. It’s uploaded to the Authntk server.
Authntk uses Amazon Web Services for Storage (Amazon S3, Simple Storage Service) and Computing (Amazon EC2 Virtual Servers in the Cloud). AWS is also used by high-profile, reliable companies such as Netflix, Twitter, General Electric, NASA, and ESPN. AWS owns almost 47% of the cloud computing global market.
Our AWS Server is called a Tier 3 XL, and it serves to process a lot of data simultaneously. We’ve upgraded our server several times based on the size of our customer base and the amount of videos we have coming through. Video processing time is a priority and we will continue to upgrade as needed.
3. Your video leaves our server for converting and encoding.
A third party called Encoding.com grabs your video from Authntk’s AWS server through something called an Application Programming Interface, or API. This is a fancy term for automatically passing data back and forth between two applications.
Encoding.com, the world’s largest cloud media processing service, does two things with your video.
• Converts the video from an .mp4 or .mov file to an HTML5 file for web and mobile viewing. If your video wasn’t converted, we would have a huge video file on our hands that cannot be streamed, embedded, sent, or viewed easily on mobile or web. HTML5 is the latest version of code that interprets web pages.
• Encodes the video to include metadata such as your customer’s name, the year, make, and model, video thumbnail, and the video frame player. A new file is created with all of this information baked into it.
Once Encoding.com is finished, the new file is transferred through the API back to the Authntk server.
4. Authntk creates a unique link.
Next, Authntk creates a unique link for the viewing page of your video. The viewing page includes your dealer-branded template with your video player. The unique link is used for reporting purposes to track video statistics, and for easy sharing capabilities.
5. The video is sent to your customer.
All videos are sent via email. If you requested SMS texting at the beginning of your Authntk service, then your video will also be sent via SMS Text Message.
6. Authntk tracks the video.
As soon as the customer receives everything, we start tracking opens, clicks, and plays through SendGrid and Authntk’s proprietary reporting. All video statistics can be viewed in your Authntk Desktop Admin along with the video, unique link, and customer information.
7. You sell the vehicle.
That’s it! We are now passing the baton back to you. We’ve delivered your video message in the quickest and easiest way possible, and now it’s time for you to work your magic.
A few cool things to note...
• This whole process takes anywhere from 45 seconds to 5 minutes, depending on data traffic at the time and video file size.
• From hitting send to customer viewing and tracking, not one human interacts with this process.
• Do you have YouTube enabled? If so, Authntk will automatically post the video to your YouTube channel at the same time it’s sent to the customer.
Have questions? Email us at firstname.lastname@example.org.