Skip to main content

Return of the Toy 2: Walmart and Mattel Ensure That The Empire Strikes Back

Article


Not content to let Target and Toys R Us have all the fun this holiday season, a new toy titanship has emerged:

Walmart and Mattel have teamed up for KidHQ, a giant, digital catalog. I appreciate that the website is unlike other things in the marketing sphere, openly pointing out that this is advertising. We are here to sell to you. All for brand engagement, of course. When you make people think a brand is their friend, they're likely to buy.

After all:

Marketers receive aggregated, anonymized data on purchases through KidHQ and how visitors interact with different toys, [Ivy] Sheibar said

And data is worth more than gold.

Time to talk about Mattel's past few years.

 In 2015, they lost a very lucrative contract - The right to make Disney Princess dolls.

Why?

“We took Disney for granted. We weren’t focusing on them,” [Chris] Sinclair says. “Shame on us.” [source]

Also, Mattel had made its own fairy tale heroine line with "Ever After High", a spin-off of Monster High. The dolls emphasized detail and commanded a higher price than Monster High right out of the gate with less of the creativity.

The story was a meandering, well-intentioned mess - Exert free will and possibly die or not? Eventually, it lost steam when it gave a half-hearted conclusion, and now that franchise is defunct.

Monster High is also (sadly) defunct - The rebranding that, in my opinion, lost 90% of what made the line special, didn't hit with audiences, despite trying to appeal to those parents who were unsure or had misogynistic things to say about them.


Walmart? Well, Walmart is Walmart - Employees do can drives for each other during the holiday because the pay is crummy.

This certainly seems more interactive than Target/Toys R Us, with kids selling to kids.

Comments

Popular posts from this blog

Connecting IoT Devices to a Registration Server (Packet Tracer, Cisco)

In Packet Tracer, a demo software made by Cisco Systems. It certainly has changed a lot since 2016. It's almost an Olympic feat to even get started with it now, but it does look snazzy. This is for the new CCNA, that integrates, among other things, IoT and Automation, which I've worked on here before. Instructions here . I don't know if this is an aspect of "Let's make sure people are paying attention and not simply following blindly", or an oversight - The instructions indicate a Meraki Server, when a regular one is the working option here. I have to enable the IoT service on this server. Also, we assign the server an IPv4 address from a DHCP pool instead of giving it a static one. For something that handles our IoT business, perhaps that's safer; Getting a new IPv4 address every week or so is a minimal step against an intruder, but it is a step. There are no devices associated with this new server; In an earlier lab (not shown), I attached them to 'H

Securing Terraform and You Part 1 -- rego, Tfsec, and Terrascan

9/20: The open source version of Terraform is now  OpenTofu     Sometimes, I write articles even when things don't work. It's about showing a learning process.  Using IaC means consistency, and one thing you don't want to do is have 5 open S3 buckets on AWS that anyone on the internet can reach.  That's where tools such as Terrascan and Tfsec come in, where we can make our own policies and rules to be checked against our code before we init.  As this was contract work, I can't show you the exact code used, but I can tell you that this blog post by Cesar Rodriguez of Cloud Security Musings was quite helpful, as well as this one by Chris Ayers . The issue is using Rego; I found a cool VS Code Extension; Terrascan Rego Editor , as well as several courses on Styra Academy; Policy Authoring and Policy Essentials . The big issue was figuring out how to tell Terrascan to follow a certain policy; I made it, put it in a directory, and ran the program while in that directory

Create a Simple Network (Packet Tracer) + A Walkthrough

Again; I've done this, but now there's so many new things, I'm doing it again. The truly new portions were...everything on the right side of this diagram; The cloud needed a coax connector and a copper Ethernet connector. It's all easy to install, turn off the cloud (Weird), install the modules. Getting the Cable section of Connections was an unusual struggle - The other drop down menu had nothing within. It required going into the Ethernet options and setting the Provider Network to 'cable', which is the next step AFTER the drop-downs. The rest was typical DHCP and DNS setups, mainly on the Cisco server down there. The post is rather short - How about adding a video to it? Find out what A Record means - This site says 'Maps a name to an IP address', which is DNS. So it's another name for DNS? You can change them (presumably in a local context) to associate an IP address to another name.