Trending December 2023 # Yugioh Master Duel – Meta Deck Guide – Lyrilusc Tri # Suggested January 2024 # Top 21 Popular

You are reading the article Yugioh Master Duel – Meta Deck Guide – Lyrilusc Tri updated in December 2023 on the website We hope that the information we have shared is helpful to you. If you find the content interesting and meaningful, please share it with your friends and continue to follow and support us for the latest updates. Suggested January 2024 Yugioh Master Duel – Meta Deck Guide – Lyrilusc Tri

Yugioh Master Duel – Meta Deck Guide – Lyrilusc Tri-Brigade

Learn how to play one of the best decks in Master Duel

The Yugioh Master Duel meta is a diverse one currently. But for those who want to get to the top ranks of competitive play with no experience, it can be difficult. Well don’t worry, these guides will take you through Master Duels best decks, their goals, combos, and what you should be seeing at the end of your turns.

The type of card in a deck will be broken down into a few categories:

Searcher – This card lets you search your deck for another card

Extender – This card will special summon itself or another card

Starter – A card that will begin your combo

Interrupter – A card that allows for interaction on your opponent’s turn, be this negate, destroy, or return a card to the hand.

Finisher – A card intended to finish up games by attacking

“Bird Up”

A hybrid of two archetypes, Tri-Brigade and Lyrilusc. Currently shredding through the Master Duel Meta and it’s currently one of its best decks. Able to end of power boards that lock your opponent into summoning wind monsters and a hefty number of negates. This deck is hard, its got a lot of combo lines that depend entirely on your starting hand. But if you think you have the brains and the will to throw sparrows and wagtails at your opponent lets begin.

Tri Brigade

Tri-Brigade is a series of monsters consisting of 3 types, Beast, Beast-Warrior, and Winged-Beast which will now be referred to as Tri type. When in the Graveyard Tri type monsters can banish themselves and other Tri-type monsters to special summon a link monster as long as it is of those same 3 monster types and the number of cards banished equals the link rating. For example, you banish 3 Tri-type monsters, you can now special summon a Link 3 Tri-type monster from your extra deck.


Lyrilusc is a series of level 1 Winged beast monsters who normally swarm the field to summon rank 1 XYZ monsters. While we will still be XYZ summoning to main focus is the swarming ability of these tiny birds. A lot of the Lyrilusc effects don’t name lyrilusc’s but specifically level 1 winged beasts, this is important for why these arcetypes and so powerful together.

The Synergy

These decks work together so well because of Tri-Brigade Nervall, a level 1 winged beast, can be searched by the Lyrilusc Recital Starling. This makes your Tri-Brigade Combos easy to start since your combo starter in Nervall is accessible every game.

The Deck

Lyrilusc cards

Main deck

Lyrilusc – Cobalt Sparrow (Searcher)

Lyrilusc – Sapphire Swallow (Extender)

Lyrilusc – Turquoise Warbler (Starter & Extender)

Lyrilusc – Celestial Wagtail (Searcher)

The ratios of these vary but 3 of each is a good start for and Lyralusc deck. Warbler is your starter, on your turn you special summon it and another Lyrilusc from your hand or Graveyard. The card you would normally summon like this is Cobalt Sparrow, who can then search any Winged beast. Wagtail searches for your Lyrilsuc spell when special summoned. Swallow is a good follow-up and search target for your sparrow.

Spells and traps

Lyrilusc – Bird Call (Starter/Searcher/Extender)

The only spell you really run in this searcher/starter combo. Incredibly powerful to add any lyrilusc to your hand and special summon a different one. As you can see from the monsters above this is incredible.

Extra Deck

Lyrilusc – Ensemlue Robin (Interupter)

Lyrilusc – Assembled Nightingale (Interrupter)

Lyrilusc – Recital Starling (Searcher)

The most important extra deck monster is Starling, your searcher for Nervall and a key combo peice. Robin is a powerful interrupter, returning opponents’ cards to their hand and recovery when it is sent to the grave. Nightingale can attack directly multiple times. With 5 materials on nightingale you can attack 5 times for 1000 damage each.

Tri-Brigade cards

Main deck

Tri Brigade Fractal (Starter)

Tri Brigade Kit (Extender)

Tri Brigate Nerval (Searcher)

Tri Brigade Kerass (Extender)

As said before Nervall is key to this deck. Being searched from any two Lyriluscs, then when sent to the grave searches any other Tri-Brigade. Frackall gets your grave loaded up with Tri-Brigades, especially when used with Kitt who also sends a Tri-Brigade to the grave. Kerass is an odd one out but he can be summoned by discarded any Tri-type which can be useful in niche scenarios.

Spells and traps

Tri-Bridage Revolt (Interuption)

Revolt is this decks secret weapon. You need to banish Tri-types to use the effects of your Tri-Brigade monsters, so you have a pretty full banished pile. Well, Revolt lets you summon all of those banish monsters back and then use them to immediately link summon. An incredible surprise on your opponent’s turn after they use all of their resources to dismantle your board only for you to flip up Revolt as summon a link 4.

Extra Deck

Tri-Brigade Shuraig (Interruption)

Tri-Brigade Bearbrumm (Searcher)

Tri-Brigade Ferrijit (Extender)

When summon Shuraig banishes an opponent’s card, this is powerful when he is summoned by Revolt to interrupt your opponent. Bearbrumm searches revolt when she leaves the field, need I say more. Ferrijit is an extender as she lets you get ant Tri-types onto the field from your hand.

Additional card

Not every card in this deck belongs to these archetypes, hand traps for example are a must, with Ash Blossom and Maxx C.

Simorgh the bird of Sovereignty is a powerful link 3 that protects any winged-beast card under its arrows from being targeted. During your end phase is also summons a winged beast from your deck, whose level is equal to the number of free spell and trap zones. And since you only want to have one filled up with Revolt that leaves you to summon a level 4. Specifically, Barrier stature of the Stormwinds is a card that locks your opponent into summoning only wind monsters, if they have none then they cannot play.

Number F0 Utopic Future Dragon is another powerful boss this deck can go into, usingF0 utopic future you can rank up into Utopic future Dragon. Future Dragon lets you negate a monster effect then take permanent control of that monster.

These are your boss monsters, aiming for these is the goal of your deck. Any other cards you add are up to you and depend on what you want in a deck.

Full Deck List

x3 Lyrilusc – Cobalt Sparrow (Searcher)

x3 Lyrilusc – Sapphire Swallow (Extender)

x3 Lyrilusc – Turquoise Warbler (Starter & Extender)

x3 Lyrilusc – Celestial Wagtail (Searcher)

x3 Lyrilusc – Bird Call (Starter/Searcher/Extender)

x3 Tri Brigate Nerval (Searcher)

Tri Brigade Kerass (Extender)

Tri Brigade Fractal (Starter

Tri Brigade Kit (Extender)

Tri-Bridage Revolt (Interuption)

Extra Deck

Tri-Brigade Shuraig (Interruption)

Tri-Brigade Bearbrumm (Searcher)

Tri-Brigade Ferrijit (Extender)

Lyrilusc – Ensemlue Robin (Interupter)

Lyrilusc – Assembled Nightingale (Interrupter)

Lyrilusc – Recital Starling (Searcher)

There is too much to cover in one article so hopefully, the basics will be useful as you learn more and more about your deck. This combo only requires two cards, this makes them much more reliable when it comes to playing the game.

Turquoise Warbler and Fraktall

With just these two you can end on a Utopic Future Dragon and the Simorgh Lock. Using Fraktall you can send a Cobolt Sparrow from deck and itself to the grave. Then using Warbler you can summon itself and the sparrow, with sparrow letting you add a Nervall to hand. Using Warbler and Sparrow you can make a Starling XYZ which searched for you Swallow. Swallow summons itself and Nervall to make another Starling. Nerval is detached from your starling to search for a Wagtail and Nerval searched for a Kitt. Those two Starlings can now be turned into Utopic Future and that into Utopic Future Dragon.

This is the start of a combo that just keeps ongoing. With enough Tri-Types in the grave to summon an extra deck monster and enough Xyz on feild to make Future Dragon it’s very clear why this is one of Master Duels’ best decks.

It’s hard to learn and explain Combos in text so here is a video by Sir Emanon explaining over 40 separate combos over a 2 hours long video.

The Price and the packs

Moonlit Avian dance is the secret pack that Lyrluscs are in along with the standard pack stalwart force. Cracking these open and getting what you need is useful but if you just want to craft the deck here is the amount of CP you will need for the basics of this deck.

N-CP : 450

R-CP : 120

SR-CP: 390

UR-CP: 210

As you can see this deck is very cheap when it comes to the main deck. Most of the cards are normal to rare with some being Super rare. The most expensive cards are in the Extra Deck, Starling is UR and you need two in order to really have a consistent deck. Simorgh and Shuraig are also UR, each of these is needed for the deck to be at full power.

Here we can see an example of a list with handtraps for extra interaction and searchers such as Fire Formation- Tenki for finding Fraktall.

I also cannot afford 8 URs

Are there any of the best decks you would like to learn how to play? Comment below and we will get started on breaking that deck down

Whilst that’s it for this, we’ve been covering a fair bit of Master Duel content, you can find it all here:

You can also read our official Yugioh Master Duel review here.

You're reading Yugioh Master Duel – Meta Deck Guide – Lyrilusc Tri

Introduction To Master Data In Sap

What is Master Data?

Data stored in SAP R/3 is categorized as

Master Data and

Transactional Data.

If you are producing, transferring stock, selling, purchasing, doing physical inventory, whatever your activity may be, it requires certain master data to be maintained.

Example of Master Data

Material master data

Customer master data

Vendor master data

Pricing/conditions master data

Warehouse management master data (storage bin master data)

The ones we will focus in MM module are material master and purchase info record.

Material Master: What you should know about material master?

Material in SAP is a logical representation of certain goods or service that is an object of production, sales, purchasing, inventory management etc. It can be a car, a car part, gasoline, transportation service or consulting service, for example.

InInIn All the information for all materials on their potential use and characteristics in SAP are called material master. This is considered to be the most important master data in SAP (there are also customer master data, vendor master data, conditions/pricing master data etc), and all the processing of the materials are influenced by material master. That is why it’s crucial to have a precise and well maintained material master.

In order to be confident in your actions you need to understand material master views and its implications on processes in other modules, business transactions and a few more helpful information like tables that store material master data, transactions for mass material maintenance (for changing certain characteristics for a large number of materials at once).

Material types

In SAP ERP, every material has a characteristic called “material type” which is used throughout the system for various purposes.

Why is it essential to differentiate between material types and what does that characteristic represent?

It can represent a type of origin and usage – like a finished product (produced goods ready for sale), semifinished product (used as a part of a finished product), trading goods (for resale), raw materials (used for production of semifinished and finished products) etc. These are some of the predefined SAP material types among others like food, beverages, service and many others.

We can define our custom material types if any of standard ones doesn’t fulfill our need.

Most used material types in standard SAP installation

What can be configured on material type level (possible differences between types)?

Material master views: It defines the views associated with a Material Type. For example, if we have a material type “FERT” assigned to our material Product 1000 – we don’t want to have Purchasing based views for that material because we don’t need to purchase our own product – it is configured on material type level.

Default price control: we can set this control to standard or moving average price (covered later in detail), but this can be changed in material master to override the default settings.

Default Item category group: used to determine item category in sales documents. It can be changed in material master to override the default settings.

internal/external purchase orders, special material types indicators, and few more.

Offered material types in MM01 transaction

So material type is assigned to materials that have the same basic settings for material master views, price control, item category group and few other. Material Type can be assigned during the creation of the material in t-code MM01 (covered in detail later)

Where can we find a complete list of materials with their respective material type?

There are numerous transactions for this. The raw data itself is stored in MARA table

(you can view table contents with t-code SE16 or SE16N – newest version of the transaction), but in some systems these t-codes aren’t allowed for a standard user. In such cases, we can easily acquire the list with t-code MM60 (Material list). MM60 is used particularly often as it displays a lot of basic material characteristics.

Selection screen – you can enter only the material number:

Selection screen for MM60 transaction

We can see that material 10410446 in plant AR01 is of type FERT (finished product).

MM60 report results with the export button highlighted

Using the toolbar button highlighted on screen, we can export the list of materials we have selected on screen.

Material group

Another characteristic SAP material is assigned during it’s creation is “material group”, which can represent a group or subgroup of materials based on certain criteria.

Which criteria can be used to create material groups?

Any criteria that suit your needs for reporting purposes is right for your system. You may group materials by the type of raw material used to produce it (different kinds of plastics used in the production process), or you can divide all services into consulting services (with different materials for SAP consulting, IT consulting, financial consulting etc), transportation services (internal transport, international transport), you can also group by production technique (materials created by welding, materials created by extrusion, materials created by injection etc). Grouping depends mainly on the approach your management chooses as appropriate, and it’s mainly done during the implementation, rarely changes in a productive environment.

Assigned material group in material master

In addition, there is a material hierarchy (used mostly in sales & distribution) that can also be used for grouping, but it’s defined almost always according to sales needs as it is used for defining sales conditions (standard discounts for customers, additional discounts, special offers).

On the other hand, material group is mainly used in PP and MM module.

If you need to display material groups for multiple materials, you can use already mentioned t-code MM60. You just need to select more materials in selection criteria.

Material group in report MM60

Material group is easily subject to mass maintenance via transaction MM17. More on that in the material master editing section.

Meta Report: The Shifting Sands Of Mainframe Software

Summary: OS/390-z/OS vendors are increasingly utilizing different tactics (e.g., subscription charges) in an effort to improve revenues. As customers continue to rely on mainframe technology, caution must be exercised to ensure existing products and technology are protected.

The continuing tight z/OS (new operating system) growth market and general economic conditions are pushing software vendors to tweak policies at the expense of customers. The newer tactics carry longer-term cost and infrastructure issues that will impact IT organizations into the future (e.g., lessened support, new-version charges). Customers must position and prepare for potentially difficult negotiations around these topics.

We believe that, by mid-2002, OS/390-z/OS independent software vendors will increase pressure to renegotiate enterprise licensing agreements due to expire by 2004. Modest z/OS growth rates will result in increased use of alternative tactics to force customers to sign agreements (e.g., version upgrade charges) and, through 2002, vendors will continue to change pricing models and support procedures to improve overall profitability.

By 2006, 30% of mainframe software products, predominantly those inherited from acquisitions, will lack adequate vendor support resources. Through the same period, 20% of OS/390 products will be relabeled and charged as new z/OS products. Through 2005, customers failing to recognize and negotiate firm contract terms and conditions will pay 20%-30% higher product costs and incur a higher risk of failed support.

During the past three years, competition has dramatically increased within the OS/390 tool market, pressuring these vendors’ financial results. z/OS software vendors were not accustomed to competition and, though many vendors are adapting, most are not well prepared for a truly competitive environment. Coupled with competition, the customer base is beginning to dwindle. The smaller, higher margin (from a vendor perspective) customers are finding total cost of ownership of Unix/Win2000 solutions a better fit for business needs. The remaining mainframe customers typically have established and seasoned negotiators that decrease overall margins for vendors. This leaves vendors with a smaller subset of customers, resulting in a flat revenue stream.

Legacy product suites are also becoming more onerous to support as customers continue to use obscure products. Low-utilization products add significant vendor burden as the customer base falls below critical mass, leaving vendors with a unsavory decision – reduce product support levels, which is unacceptable to customers, or reduce profits to retain customer satisfaction, which is unsatisfactory to shareholders. Although most mainstream products will remain well supported, customers are finding that little-used products brought in during data center consolidation can often carry support problems. (This is especially true when the product development had stagnated on a previous version of operating systems.)

In close association with an overbroad product suite, recent problems recruiting and retaining experienced mainframe personnel are problematic for vendors. The mainframe analyst experience pool is retiring, leaving younger, less experienced analysts with fewer mainframe skills. Increasing pressure resulting from vendor reductions in force and employee dissatisfaction will continue the struggle of supporting legacy products, while additional talent drain will result from the increasing shift to Unix/Windows Data Center Edition product lines.

The confluence of issues will drive OS/390-z/OS independent software vendors to reduce overall costs. We project that a marked increase in activity will occur across several customer areas. The first, subscription licensing, carries significant impact to customers. Although initial representations will indicate that the shift toward subscription is a revenue-smoothing exercise, customers will typically lose rights during the transition, ultimately leading to higher costs (though the near-term costs may seem palatable). In addition, due to the nature of subscription licensing, there is no commitment or assurance that the product will even be available for licensing in the future. This loss of control over product use rights can lead to higher costs or, worse, loss of rights to use the products, thereby creating business interruption. Customers considering subscription licensing must ensure safeguards are in place to protect long-term interests. Any enterprise license agreement negotiations must also incorporate terms and conditions to ensure support for all products continues through the end of agreement. We recommend customers pursue penalty clauses to ensure compliance.

There is an increasing trend toward new product charges for subsequent versions or new operating systems. Several years ago, Sterling Commerce led the charge on this paradigm with the upgrade charge for Connect:Direct for MVS to S/390 charges. More recently, charges have been seen for upgrades to new versions on former Platinum products. Asset managers must review all new contracts for weak terms and conditions that allow any charge for upgrades, ensuring that rights to subsequent products are clearly defined (not then current vendor policy).

Another area where customers will see surprises will be in subcapacity licensing. Although many customers believe subcapacity licensing will improve existing costs, we believe 50% of customers will find improved costs only through new licensing arrangements. Customers will be forced to acquire new licenses to qualify for subcapacity licensing. While this is arguably optional, many customers will want to exploit it as z-Series mainframes increase in penetration. We recommend customers cautiously plan and execute migration to z-Series mainframe, integrating the plan with strong software asset management principles.

To prevent surprises, customers should utilize portfolio management tactics to balance the risk of waning vendor support and potential increased cost. Customers should understand the time to retirement and the cost to convert software, and that they may experience support disruption. Included in this analysis should be the cost of business interruption in event of product failure. Customers should monitor response time on product support questions to understand whether there is a deterioration in the level of support. User groups can also be beneficial in determining adequacy of a vendor’s staffing level. Vendor mail notifications should be reviewed for critical information on product sunset dates (these letters are often lost in corporate mailboxes). In addition, customers should ask the vendor direct questions regarding whether existing products will be supported long term or under new operating systems (e.g., z/OS).

Business Impact: Tight economic conditions are spurring a contraction of software vendor support policies, leading to potential business interruption and increased systems cost.

Bottom Line: Asset managers must increase efforts at controlling contract terms and conditions to ensure cost, risk, and vendor support are tightly defined, preventing untimely business interruption and budget surprises.

Casino Stacks The Deck With New Ids System

The saying goes, ‘What happens in Vegas, stays in Vegas’.

For the casino owners, though, the saying should be more along the lines

of, ‘What money they make in Vegas should stay in their bank accounts’.

So when computer hackers try to steal vital information out of the

customer databases of the major Las Vegas hotels and casinos, it’s a big

concern. To combat the hackers — and to keep their information and

money in place — the casinos have worked hard to develop sophisticated

security systems.

The Riviera Hotel & Casino, for example, is one of them. The hotel,

which will celebrate its golden anniversary next year, has more than

2,000 guest rooms.

Like most other businesses of any significant size, the Riviera was

subject to a wide range of attacks from purveyors of malicious

code. But being a player in the glaring lights of Las Vegas, draws even more attention from the blackhat crowd.

”We’re being constantly attacked,” says Tim Wilbur, network

security specialist with the Riviera.

The company recently decided to shop for an intrusion detection system

(IDS) to better identify and manage the threats. The Riveria’s security

staff had been monitoring attacks by ”drudging” through firewall logs,

watching the network for traffic spikes and trying to monitor the

network infrastructure.

”But we wanted to take the guesswork out of our security approach,”

says Wilbur. ”I wanted to know the when’s, where’s, how’s and how


The staff decided to look at a few alternatives for intrusion detection

solutions. They considered a product from Recourse Technology, but after

Symantec acquired that company, the Riviera staff detected a dropoff in

customer service and got turned off. They also looked at the Snort open

source software, and its GUI with log consolidation. But in the end, the

team decided on Sentivist from NFR Security.

”Ultimately, we went with NFR based on price and product,” Wilbur

says. ”NFR offered more information in a consolidated way for less

money. The level of detection was more in-depth and provided more

information, including information about ‘false positive’ situations and

a reference guide with information on suggested corrective actions.”

The implementation required a ”crash course in Linux,” since Sentivist

uses a hardened Linux OS within its appliance. That, however, did not

prove to be much of a stumbling block for the Riviera team. The product

has met the IT team’s expectations, and they report a positive


”The Riviera is not just a hotel. It is in the gaming industry,” says

Andre Yee, CEO of NFR. ”So there are many credit card transactions in

their environment, and other confidential financial information related

to clients and guests. They all need to be protected, and a firewall is

not enough. A skillful attacker can circumvent a firewall.”

NFR differentiates on its use of both protocol anomaly detection and

signature pattern matching, in a hybrid approach. The product is priced

at $11,000 for 100Mbps throughput, to $22,000 for 1Gbps throughput.

The biggest trend in the IDS market is the move to intrusion prevention,

says Andrew Braunberg, senior analyst for information security with

Current Analysis, an industry research firm based in Sterling, Va.

These competitors, in addition to NFR in the IDS market, include Cisco

Systems, Inc., ISS, Inc., Network Associates Technology, Inc., and

Symantec Corp. NFR does have plans to move into intrusion prevention in

the second half of this year.

security administrators are not comfortable putting an appliance in

line, so we put in a mechanism that allows customers to calibrate the

risk of dropping legitimate traffic.”

A key trend is the ability to reduce false positives and prioritize

threats, says Braunberg of Current Analysis.

”If you have vulnerability assessment data married to threat management

data, that allows you to prioritize what the really important threats

are to the network at any one time,” Braunberg says. ”That is what an

effective IPS does, theoretically. And all these companies are looking

at that.”

implementation: ”Product demonstrations are absolutely necessary.

Intrusion detection can become very labor intensive due to the amount of

information passing through the lines today. In my case, consolidation

and explanation was key.”

Meta Facebook Pixel Tracking With Google Tag Manager

The Facebook Pixel is a multi-purpose tool that helps you optimize your campaigns and analyze your audience data. You can enhance the Facebook Pixel by integrating it with Google Tag Manager, which makes tracking easy, consistent, and powerful.

There are three ways to install the Facebook Pixel tracking with Google Tag Manager, which we demonstrate in this complete training guide.


If you use the Facebook Pixel and haven’t integrated Google Tag Manager yet, it’s time to streamline your workflow and maximize your marketing power.

This tutorial will use a demo store running on WordPress and WooCommerce. We also use an almost-empty GTM Container, which is already implemented on this store using the free Google Tag Manager for WordPress plugin by Thomas Geiger.

Let’s dive in.

Tracking with Facebook Pixel (3 Methods)

In this post, we will cover three different methods to install the Facebook Pixel with Google Tag Manager. You can skip to the most relevant method if you know what you’re looking for, or you can read through to figure out which method will best suit your tracking needs.

The first method is automatic installation using the Facebook integration. It is the simplest and fastest, but it is quite limited in functionality: you can track pageviews, but not other types of events.

The second method is manual installation directly through Google Tag Manager. This is much more flexible and powerful, so we recommend it if you feel comfortable working with a little bit of code.

The final method uses Custom Tag Templates through Google Tag Manager’s Template Gallery. It is fast and easy, but still very customizable. Custom Templates are an incredibly user-friendly way to track all kinds of events.

1. Automated Facebook Pixel Installation Pros and Cons of Automated Installation

Before moving forward, let me tell you why I usually avoid this method.

When you authorize Google Tag Manager and verify it for Facebook, Facebook goes into Google Tag Manager and creates Tags and triggers on its own. It assigns triggers to the Tags and publishes your Container immediately.

If you have any changes or works-in-progress in your Container, or if someone else is already working in your Container, then you don’t want to publish it immediately to a website. Doing so can make things complicated, and possibly even break things that you already had in place.

If you already have Tags or triggers in your Container, you should skip ahead to a different method. I’d also recommend either of the other two methods for anyone who wants more customization and control.

But if you have an empty Container, this shouldn’t affect you. This method is still a great option if you don’t have a lot of time and you only want to track pageviews instead of events.

Install Facebook Pixel with Google Tag Manager

On our data sources page, we’ll select the pixel that we want to install.

Connect and Verify Google Tag Manager Account

Now, we will see a list of icons for different platforms and tools that already integrate with Facebook. Among these is Google Tag Manager.

Next, Facebook will try to help us set up some extra events, which we won’t worry about at the moment. For now, we just want to go back to Google Tag Manager and refresh our page so we can review the tags and see what Facebook has done.

And here in Google Tag Manager, we’ll see that the Facebook Pixel tag has already been created. The Workspace Changes in the upper-right corner are zero, which means the workspace has already been published.

This is another reason that I don’t really like the automatic installation method. It doesn’t give you much control or flexibility, and it auto-publishes a work-in-progress Container. This can cause confusion or complications later down the road, so be aware of it if you use this method.

2. Manual Facebook Pixel Installation

If you want more flexibility and more analytical power using your Facebook Pixel and Google Tag Manager, the manual installation method is the way to go.

When prompted, we’ll choose the second option in the popup: Manually add pixel code to website. 

Adding Pixel Code to All Pages

Because Google Tag Manager doesn’t already have any built-in Tags for Facebook, we need to build our own Custom Tag that can use our JavaScript code from Facebook.

Advanced Tip: Pixel Components

If you know JavaScript, you should always look over someone else’s code before you put it on your website. You might not change anything, but it’s good to know exactly what your code is doing. Most importantly, you may notice that Facebook’s code may break in certain cases.

To find out why, let’s take a closer look at the Facebook Pixel code.

Let’s start with the first part of the script segment,  from lines 3 to 10. We have a function, !function(f,b,e,v,n,t,s), for Facebook events. This will load a JavaScript library from Facebook’s servers.

Once the library is loaded, we have the pixel initiation code on line 11. fbq(‘init’ initiates the code, and the following number is your Facebook Pixel ID. This line of code uses the loaded library to activate your specific pixel on your page. When the Facebook Pixel is activated, it will listen to events, collect them, and report them to the Facebook Events Manager.

Line 12 is an event. It tells Facebook to track a pageview and send it to your activated pixel.

Since that looks good and we understand the code, we’ll check out the noscript portion next.

But the Google Tag Manager Container is made of JavaScript, and it executes Custom HTML when JavaScript is supported. So if you think you may have a lot of users whose browsers don’t support JavaScript,  you’ll want to take this piece of code out and put it in an image Tag instead.

So in this case, we’ll delete the noscript portion, which is lines 14 through 16 of the original HTML code. Our code should end up looking like this:

To be honest, this isn’t a super critical step. Most browsers support JavaScript, and for those that don’t, your website probably won’t function correctly anyway. However, it’s certainly something to be aware of so that you can support users when they encounter problems.

Testing Testing with Preview & Debug Mode

Let’s go to our website and refresh the page there to preview the Container. If everything is working, you will see that the Tags fired both in your Google Tag Manager bar and in the Facebook Pixel Helper. (If you don’t have the Facebook Pixel Helper Chrome extension, we recommend it! Get it here.)

Testing with Facebook Pixel Helper Extension

If we investigate the Facebook Pixel Helper, we can see that a pageview event has been fired and that some microdata has been automatically detected.

Under the pageview dropdown, there’s some information about the pageview. You’ll find information like the recorded URL, the pixel code, and pixel location.

Top Tip: How “Microdata Automatically Detected” Works

The blue lightning icon identifies automatically-detected events in Facebook Pixel Helper. The green checkmark icon identifies events that we set up and fire ourselves using Google Tag Manager.

Testing with Facebook Test Events

Refresh your shop page, then come back to the Facebook Events Manager. If events are being properly recorded and sent to Facebook, you’ll see a pageview with the URL of the page you just refreshed.

Event Debugging

Select the pixel that you’re currently using.

Once you’ve found this solution, it may be tempting to just rely on Facebook’s automatic microdata detection for all of your event tracking instead of manually setting up a bunch of events through Google Tag Manager. This is a really bad idea for your analytics.

It’s always better to manually set up tracking for events that are important to us. If you want to use events data to set up conversion tracking or to create Custom Audiences, you need your data to be as reliable as possible. The best way to make sure that information is being recorded the way you want is to set it up yourself.

Custom Event Pixel Installation

Now, if you only want pageviews to be tracked to your Facebook Pixel, you can stop here. You can use pageviews in the Facebook Events Manager to create a few Custom Conversions, create Custom Audiences, and run Remarketing Ads.

But the Facebook Pixel can do so much more for you beyond tracking pageviews.

Basically, the possibilities are endless when you include events in your Facebook Pixel tracking. Let’s learn how to implement this valuable tool.

What Kind of Events Can You Track on Your Website?

There are two types of events that we can track to a Facebook Pixel: Standard Events and Custom Events.

We can also still track other events even if Facebook doesn’t recognize them as Standard Events. For example, if we want to track users that spend five seconds on our landing page, we can configure a custom user interaction event.

Some possibilities for creating Custom Facebook Events include:

Time on Site

Scroll Tracking

Element Visibility

We can create these kinds of Custom Events and more. And if you used manual installation or Custom Tag Templates to implement your Facebook Pixel, it’s not as hard as you might think. Let’s learn how.

Step-by-Step: Setup Event Tracking

To track events, we’ll start in Google Tag Manager. Remember that we can’t set up event tracking this way if you used the automated installation process, but it’s pretty easy if you used either manual installation or Custom Templates.

The first thing we need to do is split our Facebook Base Pixel code into two parts. Our goal is to  separate the initiation part of this pixel from the first event, which is the pageview.

This is because we want to track more events different from the pageview. Those events will also require the Base Pixel to be initiated; otherwise, they won’t function correctly.

So the sequence is like this: the Facebook Pixel must be initiated before an event can fire in order to pick up that event and report it to Facebook. We only need execute the Base Pixel once, but as long as it initiates first, it will record every other event that fires on a page.

When you open the Tag configuration settings, you’ll be able to directly edit the HTML code. We need to take out the Facebook pageview tracking code and add it to its own Tag.

Next, we’ll create a new Tag to host the pageview section that we just cut out of the Base Pixel code. Name it something like FB – Pageview and choose Custom HTML as the Tag type. 

Now we have both the Facebook Base Pixel and the pageview event firing separately on all pages. However, we have to find a way to ensure that Facebook’s Base Pixel always fires before the pageview event.

When we see our Tags in the dashboard like this, we have no way of knowing this because Google Tag Manager fires Tags asynchronously. It is not possible to tell which one fires first and which one fires second on the default settings.

So our next order of business is assigning an order of firing to these two Tags. We have two possible solutions to this problem.

Method 1: Firing Priority

The first way is called Tag firing priority. By default, the firing priority of each Tag is zero. We can assign a priority using any integer, with the highest value firing first and the lowest value firing last.

This works for some situations, but we’re not going to use it in this tutorial. Tag firing priority ensures that Tags fire in a certain order, but it doesn’t guarantee that a Tag will finish its execution before the next Tag is initiated.

This means that it is possible for your pageview Tag to fire before your Base Pixel Tag has finished executing. If this happens, the pageview Tag won’t be picked up or reported to the Facebook Pixel, and you will lose tracking data.

Method 2 (Recommended): Tag Sequencing

So we will use the second method, which is Tag sequencing. With Tag sequencing, we can assign an order to Tag firing, and Google Tag Manager will ensure that the first Tag has been fired and executed completely before it fires the next Tag.

These settings allow you to choose Tags that either must precede or must follow your Tag. Since the Base Pixel must be initiated before the pageview Tag, the Base Pixel is called a set-up Tag. You will need the Base Pixel to be selected as a set-up Tag for any events that you want tracked by the Facebook Pixel.

In this case, I recommend checking the box to not fire your current Tag if the set-up Tag fails. If the Facebook Base Pixel fails to execute, there is no way the pageview Tag’s HTML code will work on its own. It doesn’t know where to send data, and there is no base Tag to listen for this event.

Okay, so that’s it. So we’ve set up Tag sequencing to ensure that Facebook Base Pixel always fires and finishes execution before the Facebook pageview Tag.

Set Base Pixel Tag to Fire Once per Page

For all of those events, we also need to set our Facebook Base Pixel as the set-up Tag. If we change nothing else, then our Base Pixel Tag will fire multiple times—once for each event that uses it as a set-up Tag.

This is inefficient. If the pixel is initiated already, it should pick up all following event Tags, and we don’t want it to fire extra times.

Now Facebook Base Pixel will fire just once per each page, and it will finish executing before any other event Tag fires on that page. Even if another event has defined the Base Pixel Tag as its set-up Tag, Base Pixel will fire just once per page.

Set Up Facebook Standard Event Tag

Let’s set up a new Standard Event to go with our fully-functional Base Pixel and pageview Tags. Since our demo page is a shop, let’s use Facebook’s Add To Cart Standard Event for our Tag.

Create Add-to-Cart Button Trigger

Refresh your Container so that your trigger is live. Now, we can make a Tag for this trigger that will be reported to the Facebook Pixel.

Let’s name this FB – Add To Cart. Since add to cart is a Standard Facebook Event, we only have to edit the HTML code by replacing  PageView with AddToCart (again, these are case-sensitive).


We should also be able to see our add-to-cart Tag in the Facebook Events Manager. We can tell that Facebook has recognized the Tag as a Standard Event because of the shopping cart icon next to the name instead of a Custom Event icon. 

Set Up Facebook Custom Event Tag

Now that we can add a Standard Facebook Event, let’s set up a Custom Event for the Facebook Pixel to track. This time, we’re going to add an event that tracks when a user spends at least five seconds on a page, which can be more informative than a pageview.

Create New Tag

Again, we want to use the Custom HTML Tag type for this event. However, because this isn’t a Standard Facebook Event, we need to replace ‘track’ in the code with ‘trackCustom’. Then we’ll name our event in the code ‘5-Seconds’.

We also need to make sure our Tag sequencing is set up properly. Assign your Base Pixel Tag to execute as a set-up Tag before our timer Tag. Remember that we don’t want to fire this Tag if the Base Pixel set-up Tag fails, since this Tag will function incorrectly without the Base Pixel.

Create and Apply Timer Trigger

Let’s name our trigger Timer – 5 Seconds and select Timer for the trigger type. For the timer to count down five seconds, enter 5000 in the Interval field since it asks for milliseconds.

We only need this trigger to fire once per page, so set the Limit to 1. I want this trigger to fire in all pages and situations, so we will write this as Event matches RegEx .*


Okay, let’s go back to the website, refresh the page, and see what happens.

In Google Tag Manager, we have our five seconds event, our Base Pixel, and our Facebook pageview. The Facebook Pixel Helper shows the pageview, the five seconds, and some microdata.

Refresh your website page, then wait for the Tag to fire and appear here in Facebook Events Manager. If everything is debugged and working properly, you will see your five seconds Custom Event here.

Top Tip: The Multi-Pixel Problem

So far, we have only used one Facebook Base Pixel. But sometimes you might need more than one Base Pixel to fire on a single page.

But each of these pixels accounts should initiate their own Base Pixel for the events they track to function properly.

Now, if we preview the Container and refresh the page, you’ll see in the Facebook Pixel Helper that we have two pixels initiated on this page. Each pixel detected the pageview and five second timer, but it seems that the pageview fired before the second Base Pixel finished executing.

Facebook will say here that they detected the pageview event code, but no pixel was activated for it. This data gets especially confusing because the five second timer was still recorded by the second Base Pixel, since it had time to finish executing before the event fired.

So you can already see that lots of things can go wrong when we have multiple pixels. Some Tags may fire before the Base Pixel finishes loading, some Tags might fire to all pixels instead of just one, or some of Tags could fail to fire to the pixel that they were supposed to find.

The Solution

Okay, so what’s the solution? We’ll have to rely on the code ‘trackSingle’.

If you take another look at our event tracking code, the piece from Facebook starts with fbq(‘track’,. We can change this to fbq(‘trackSingle’, which tells this event to find a single, specific pixel.

Now the page view event will only fire to our first Base Pixel. You can make this same modification to most other event Tags using whatever Pixel ID you need.

There is a slight modification for Custom Events. For Custom Events like our five-second timer, we need to use the code ‘trackSingleCustom’, to send the event to a single pixel.

To demonstrate how to test this, I have modified the pageview, add to cart, and five-second timer to track exclusively to our first Base Pixel, even though we will have both Base Pixels initiated.

Let’s refresh the Container, go back to our website, and refresh the page. All three Tags have been recorded to just the first pixel. You can change the HTML code for your Tags to send any event to different pixels without doubling them up or losing data.

3. Custom Tag Template

Our third method of installing the Facebook Pixel with Google Tag Manager uses Custom Tag Templates. This is a newer but incredibly useful technique that combines flexibility, power, and ease of use.

What Are Custom Tag Templates?

In 2023, Google Tag Manager introduced a new feature called Custom Templates. Custom Templates function for users basically the same as built-in Tags from Google Tag Manager.

But the difference is that anyone can create a Tag Template and share it with others via the Community Template Gallery. This means that you have access to a huge pool of experts who are solving current problems in real time.

Why Use Them? No Base Pixel Needed

The beauty of Custom Tag Templates is that they can automate Tag firing priorities, sequencing, and frequency. Manual installation requires setting each of these up yourself for every individual Tag, and in the case of the Facebook Pixel, this includes an additional Base Pixel Tag.

A Template simplifies this process and eliminates the need for a Base Pixel Tag. The Template we use in this tutorial ensures that the Facebook Base Pixel initiates before each event that you want to record. It also won’t fire extra times or before any other events. 

In other words, you just have to create Tags for the specific events you want to track. Everything else is configured automatically to make sure that the Facebook Pixel and Google Tag Manager work together.

Easy Multiple Pixel Set Up

The other nice feature of the Custom Template we use in this tutorial is that the default setting is to track single. The Tag configuration includes your Facebook Pixel ID as part of the setup, so it only fires the event to that specific ID. You can easily include multiple IDs to receive tracking data from a single Tag, or you can send different Tags to different pixel IDs.

Add Tag Template to Your Account

Now, let’s go to Google Tag Manager and start using Custom Templates.

In this tutorial, we’ll be using Simo Ahava’s Facebook Pixel Tag Template, which quickly and easily implements the Facebook Pixel using Google Tag Manager. Simo Ahava contributes a lot of high-quality Templates to the community library, and he shares a lot of knowledge about Google Tag Manager and Google Analytics on his blog. Check out his work if you’re interested in more creative solutions!

To find this Template, you can search for it by name: Facebook Pixel. The creator will be listed as gtm-templates-simo-ahava.

This is also where you can investigate who built the Template you want to make sure that you trust it. Google is pretty good about vetting Community Template Gallery submissions, but always do your reading just in case.

Set Up Facebook Pageview Tag

Working with this Custom Tag Template is really easy. Let’s create a new Tag and see just how simple it is.

First, let’s give our new Tag a name. I use “CT” here for “Custom Template.” Select the Custom Template that we just added, and enter your Facebook Pixel ID. For now, select Standard for our event and choose PageView from the dropdown (we’ll look at Custom Events in a moment).

Now that we have a pageview Tag set up with our Custom Template, let’s test it on our website. Refresh the Container, then go to your website and refresh the page.

If everything is configured correctly, Google Tag Manager and the Facebook Pixel Helper will show that our Facebook Pixel Custom Template Tag has fired. Just like that, we have a fully-functioning Tag using a Custom Template.

To demonstrate how easy it is to expand your setup, let’s make two more Tags: one Standard Event and one Custom Event.

Next, we’ll copy this Tag again to set up a Custom Event. Let’s make a Tag that records when a user has been on a page for at least five seconds.

In Google Tag Manager and the Facebook Pixel Helper, we should see our Tags recorded for the pageview, five seconds of viewing, and add to cart.

Extra Features

Now before we wrap up this tutorial, I want to show you two other features that this particular Custom Tag Template has that are difficult to accomplish through manual tracking.

Disable Automatic Configuration

Under More Settings in our Tag configuration, we can disable the automatic configuration. This disables the Facebook Pixel’s ability to automatically collect metadata, which you saw labeled as microdata in the Facebook Pixel Helper.

Wait for GDPR Consent Option

This Custom Template also has a setting that allows you to hold an event from being fired until the user gives tracking consent. You will notice that the initial setting for this field is True.

If you set it to False, it means that by default, we do not assume that the user has consented to be tracked by Facebook. In this case, the Tag will fire but it will not be executed; it will wait until another Tag with consent granted (set to True) fires.

This is really good for compliance purposes, especially with GDPR when you need to get users’ explicit consent before doing any marketing tracking.

Creating FB Custom Conversion Using Events

Let’s take a quick look on how we can use the events you’ve tracked in the Facebook Events Manager to create Custom Conversions.

FAQ How do I create a Custom Event Tag, such as a timer for tracking when a user spends at least five seconds on a page?

To create a Custom Event Tag like a timer for tracking user engagement, you need to create a trigger that fires after a certain time interval. In Google Tag Manager, create a trigger with a timer type and set the interval to five seconds. Configure the trigger to fire once per page. Then, create a new Tag with the HTML code for the Custom Event, assign the trigger to it, and save the settings.

How do I create a new Standard Event Tag, such as the “Add To Cart” event, with Google Tag Manager and the Facebook Pixel? How do I set up Tag sequencing for the Facebook Pixel with Google Tag Manager?

To set up Tag sequencing, open the configuration settings of your pageview Tag in Google Tag Manager. Under Advanced Settings, enable Tag Sequencing and select the Base Pixel Tag as the set-up Tag. Additionally, you can choose to not fire the pageview Tag if the Base Pixel fails. Save the settings to set up Tag sequencing.

How can I ensure accurate event tracking when using multiple Facebook Pixels?

When using multiple Facebook Pixels, it is crucial to specify the pixel that each event Tag should be sent to. To do this, modify the event tracking code by replacing fbq('track') with fbq('trackSingle') and include the ID of the specific pixel inside single quotes followed by a comma. This ensures that the event is sent only to the designated pixel. Make the same modification for Custom Events by using fbq('trackSingleCustom'). By doing so, you can avoid issues where Tags fire to the wrong pixels or duplicate data.

What are Custom Tag Templates in Google Tag Manager, and why should I use them for implementing the Facebook Pixel?

Custom Tag Templates are a feature in Google Tag Manager that allow users to create and share Tag Templates with others. They automate Tag firing priorities, sequencing, and frequency, simplifying the implementation process. When using Custom Tag Templates for the Facebook Pixel, you don’t need a separate Base Pixel Tag, as the Template takes care of initiating the Facebook Base Pixel and ensuring proper Tag firing.


In this tutorial, we covered three different methods of Facebook Pixel tracking via Google Tag Manager.

The first one was automatic installation. This is remarkably quick and easy to set up. It’s limited in its tracking capabilities and can disrupt a Container-in-progress, but it’s great for pageview tracking if you have an empty Container.

The second one was manual installation. This method is the most powerful and customizable, but it can be challenging to execute. There are a lot of small, detailed steps to set up and test things like Tag sequencing and tracking with multiple pixels. It may not be for the faint of heart, but if you’re comfortable working with Google Tag Manager, you can customize it exactly how you want.

The third and final method was using Simo Ahava’s Custom Tag Template. It grants just as much flexibility and power as manual installation, but it is much quicker and easier to set up. Custom Templates are the most user-friendly way to track all kinds of events with the Facebook Pixel.

There’s always more to learn with the Facebook Pixel! If you want to learn a few more tricks, check out these tutorial posts:

The Bored Ape Creators Are Taking On Mark Zuckerberg’s Meta

Yuga Labs launched the Bored Ape Yacht Club (BAYC) NFT collection in April of 2023. It was barely a year ago. However, in this short amount of time, the company has seen massive growth. And that’s putting it mildly.

Bored Ape Yacht Club is the world’s most valuable NFT collection. If you took all the NFTs in the collection and sold them, you’d make more than 1.09 million ETH. That’s about $3 billion dollars (at time of writing). As such, it’s not really surprising that a leaked pitch deck showed Yuga Labs made a net revenue of $137 million in 2023.

For 2023, they set their targets much higher. Ultimately, the company aims to bring in nearly half a billion in revenue, setting its targets at a very healthy $455 million. But how can one company possibly hope to achieve so much when, just a year ago, they effectively didn’t exist?

By taking on Mark Zuckerberg’s Meta and dominating the metaverse.

Setting sail for a new land

Yuga Labs’ massive metaverse initiative will begin with virtual real estate.

Their forthcoming virtual world is called “Otherside.” The team bills it as a MMORPG (Massively Multiplayer Online Role-Playing Game) that’s connected to the NFT ecosystem and more. In this respect, Otherside is more than just a virtual world. It’s a metaverse. “We want to build something that expands the universe of the BAYC, but also invites the larger NFT community (and those priced out of BAYC membership) to join,” the company explained in its leaked deck.

Yuga Labs plans to begin this initiative by selling virtual land as NFTs. These will be linked to plots in the Otherside metaverse game. In each case, the plots will come with distinct traits, like unique natural resources, artifacts, and rare characters. In the deck, the team noted that 200,000 plots will be distributed in two sales in March and August.

From these two sales alone, the company projects they will earn $356 million dollars.

There will also be an in-game app store that Yuga Labs plans to use to increase revenue and expand its reach in the metaverse. Individuals will be able to use the system to create characters from NFTs they own. They will also be able to accessorize these characters using NFTs.

The long-rumored ApeCoin is here

Yuga Labs has also built a wider media empire around the BAYC NFT series. They recently launched their much-hyped ApeCoin, which is called the $APE token. It will be their primary token for all of their products and services.

Introducing ApeCoin ($APE), a token for culture, gaming, and commerce used to empower a decentralized community building at the forefront of web3. 🧵

— ApeCoin (@apecoin) March 16, 2023

Notably, Yuga Labs launched this token in coordination with a host of other major players, though the company has a sizable voting share when it comes to the governance of ApeCoin. Yuga Labs also gets a significant chunk of the money earned from the coin.

These partnerships are critically important, as the partners will also be using the tokens in their projects. For example, one of the world’s largest blockchain game developers, Animoca Brands, announced that it will let users purchase NFTs in its play-to-earn (P2E) game called Benji Bananas using ApeCoin. More games and projects will likely be making similar announcements in the coming months, enabling Yuga Labs to extend their reach into the metaverse even further.

Yet, although ApeCoin will be used as in-game currency, the token will likely be more impactful as a general-purpose digital currency. ApeCoin will get listed on exchanges like Coinbase, Voyager Digital, Binance, Gemini, and eToro. The team plans to use a portion of the money it raises from it to create merchandise and events, which (of course) only increase their revenues and brand loyalty.

According to Statista, Meta generated about $115.66 billion in revenues through its family of apps in 2023. Their most notable apps (Facebook, Instagram, Messenger, and WhatsApp) dominate both the social media and communications ecosystems.

At the present time, Yuga Labs can’t really compare to that. But remember, they have only been around a year. And they’ve already started to consolidate by acquiring their competitors. This year, they bought both CryptoPunks and Meebits from Larva Labs. Although it’s too soon to predict who will ultimately control the metaverse, there is good reason to suspect that Yuga Labs at least has a fighting chance.

It remains to be seen whether they will be just and equitable rulers.

Update the detailed information about Yugioh Master Duel – Meta Deck Guide – Lyrilusc Tri on the website. We hope the article's content will meet your needs, and we will regularly update the information to provide you with the fastest and most accurate information. Have a great day!